← previous blocknext block →recent activity
Analyzing
Block #87,498,232
25 transactions · 21 stateful · 2026-07-13 13:59:03 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
0.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,498,232 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w112w213w314w415w217w320w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x375e887b…a361
0x34b655…2a6f
4 touches
1 conflict
0x375e887b…a362
0x34b655…2a6f
4 touches
1 conflict
0x4b628349…f327
0x34b655…2a6f
4 touches
1 conflict
0x71cd2af8…dbd4
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity