← previous blocknext block →recent activity
Analyzing
Block #87,498,510
21 transactions · 21 stateful · 2026-07-13 14:00:55 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,498,510 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w27w310w011w112w213w214w318w219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26bd6b5f…38ec
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x2a9f9737…d07d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x96b47eb9…c3c3
0x34b655…2a6f
4 touches
1 conflict
0xa1002523…644f
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
3 conflicts on slot 0x26bd6b5f41…6538ec
Audit this contract →
← previous block·next block →recent activity