← previous blocknext block →recent activity
Analyzing
Block #87,121,514
10 transactions · 7 stateful · 2026-07-11 19:59:18 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,121,514 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xe84ca9a7…b041
0x34b655…2a6f
4 touches
1 conflict
0xe8807992…97a3
0x34b655…2a6f
4 touches
1 conflict
0xebeee24a…ed8d
0x34b655…2a6f
4 touches
1 conflict
0x0431e51f…6f91
0x34b655…2a6f
4 touches
1 conflict
0x4c7b72e8…9a1f
0x34b655…2a6f
4 touches
1 conflict
0x581b829b…9578
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
1 conflict on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity