← previous blocknext block →recent activity
Analyzing
Block #87,077,786
10 transactions · 10 stateful · 2026-07-11 15:07:07 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,077,786 · 10 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
1w02w16w27w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x4943ce42…cab3
0x34b655…2a6f
6 touches
3 conflicts
0xaf10e1bf…0391
0x34b655…2a6f
6 touches
3 conflicts
0x0b277fb8…2d81
0x34b655…2a6f
4 touches
1 conflict
0x0b277fb8…2d82
0x34b655…2a6f
4 touches
1 conflict
0x26f57be7…b6e8
0x34b655…2a6f
4 touches
1 conflict
0x4e815ddc…2f85
0x34b655…2a6f
4 touches
1 conflict
0x66676ad3…3153
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity