← previous blocknext block →recent activity
Analyzing
Block #87,046,212
12 transactions · 12 stateful · 2026-07-11 11:36:30 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,046,212 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2efac4f6…3abf
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xcf090a80…4536
0x34b655…2a6f
4 touches
1 conflict
0x05975727…7fcf
0x34b655…2a6f
4 touches
1 conflict
0x3b787279…727f
0x34b655…2a6f
4 touches
1 conflict
0x67cea12c…0cbe
0x34b655…2a6f
4 touches
1 conflict
0x731f1834…ef5f
0x34b655…2a6f
4 touches
1 conflict
0x7985b1c9…9c1d
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 0x2efac4f6c8…eb3abf
Audit this contract →
← previous block·next block →recent activity