← previous blocknext block →recent activity
Analyzing
Block #86,513,936
9 transactions · 7 stateful · 2026-07-09 00:16:41 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,513,936 · 9 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
2w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x57bb625a…286d
0x34b655…2a6f
4 touches
1 conflict
0x7c6a17fa…e95d
0x34b655…2a6f
4 touches
1 conflict
0x13938a09…5f88
0x34b655…2a6f
3 touches
1 conflict
0x31723dcf…4e92
0x34b655…2a6f
2 touches
0 conflicts
0x35003bda…a553
0x34b655…2a6f
2 touches
0 conflicts
0x574628e9…dcc3
0x34b655…2a6f
2 touches
0 conflicts
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 0x258fcaf5fc…c22084
Audit this contract →
← previous block·next block →recent activity