<p>These are the timestamps of the last time any byte was sent or received to/from the peer over the P2P connection.</p>
<p>The distinction between bytes and messages matters for large messages, such a blocks. On a slow connection, a block may take multiple seconds to send or to be received.</p>

CC BY-SA 4.0
2024-12-23T14:13:32.163Z
Got it! Thanks!!!
yuivc
CC BY-SA 4.0
2024-12-21T22:52:22.640Z
2024-12-21T22:52:22.640Z
Pieter Wuille
<p>The Bitcoin Core RPC <a href="https://developer.bitcoin.org/reference/rpc/getpeerinfo.html?highlight=peerinfo#:%7E:text=to%20it%0A%20%20%20%20%22-,lastsend,-%22%20%3A%20xxx" rel="nofollow noreferrer">docs</a> says <em>lastsend</em> as UNIX epoch time of last send, similarly for <em>lastrecv</em>. Does that mean last sent/received P2P message or transaction?</p>

<bitcoin-core><json-rpc><bitcoin-cli>
What does lastsend and lastrecv in "getpeerinfo" rpc mean?
yuivc
# What does lastsend and lastrecv in "getpeerinfo" rpc mean?

(Asked by: username_0 on 2024-12-21)

The Bitcoin Core RPC [docs](https://developer.bitcoin.org/reference/rpc/getpeerinfo.html?highlight=peerinfo#:%7E:text=to%20it%0A%20%20%20%20%22-,lastsend,-%22%20%3A%20xxx) says *lastsend* as UNIX epoch time of last send, similarly for *lastrecv*. Does that mean last sent/received P2P message or transaction?

**Tags:** bitcoin-core, json-rpc, bitcoin-cli


---

## 1 answers

### Answer by username_1 on 2024-12-21. Score: 2 | Accepted answer

These are the timestamps of the last time any byte was sent or received to/from the peer over the P2P connection.

The distinction between bytes and messages matters for large messages, such a blocks. On a slow connection, a block may take multiple seconds to send or to be received.

> **Comments:**
> **username_0**: Got it! Thanks!!!  

---

