← previous blocknext block →recent activity
Analyzing
Block #86,221,611
24 transactions · 23 stateful · 2026-07-07 15:43:57 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,221,611 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w18w113w214w015w017w118w219w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x3915792b…0208
0x34b655…2a6f
6 touches
3 conflicts
0xb577a4a7…a670
0x34b655…2a6f
6 touches
3 conflicts
0x870b5001…aeaa
0x34b655…2a6f
4 touches
1 conflict
0x9b982dcd…3dd9
0x34b655…2a6f
4 touches
1 conflict
0xa070b969…42c5
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
15 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity