← previous blocknext block →recent activity
Analyzing
Block #87,710,402
26 transactions · 23 stateful · 2026-07-14 13:38:43 UTC
Parallelism
73/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,710,402 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w110w013w214w317w018w119w122w423w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0x039c2f44…9ac7
0x34b655…2a6f
6 touches
3 conflicts
0xa84ac543…8b65
0x34b655…2a6f
6 touches
3 conflicts
0xcf5ef070…7d4f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2f35c56f…046b
0x34b655…2a6f
4 touches
1 conflict
0x3eede796…d745
0x34b655…2a6f
4 touches
1 conflict
0x49f5a697…72c0
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
10 conflicts on slot 0x0dd44476b8…7fef40
Audit this contract →
← previous block·next block →recent activity