← previous blocknext block →recent activity
Analyzing
Block #86,624,224
22 transactions · 20 stateful · 2026-07-09 12:35:31 UTC
Parallelism
68/100
Blocked
35%
Avg conflicts / tx
0.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,624,224 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w110w111w217w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eb0ac6b…a73a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x21683d77…4e07
0x34b655…2a6f
4 touches
1 conflict
0x2533f477…a43b
0x34b655…2a6f
4 touches
1 conflict
0x2efac4f6…3abf
0x34b655…2a6f
4 touches
1 conflict
0x303f4ecc…ab9b
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
6 conflicts on slot 0x8eb0ac6bf2…4da73a
Audit this contract →
← previous block·next block →recent activity