← previous blocknext block →recent activity
Analyzing
Block #86,222,353
24 transactions · 16 stateful · 2026-07-07 15:48:55 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,222,353 · 24 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
2w03w04w17w18w29w219w320w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9fd372a1…a959
0x34b655…2a6f
8 touches
6 conflicts
0xe2307994…acad
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x336e7bce…0dc1
0x34b655…2a6f
4 touches
1 conflict
0x455d8ffa…2a47
0x34b655…2a6f
4 touches
1 conflict
0x870b5001…aeaa
0x34b655…2a6f
4 touches
1 conflict
0x8a1db511…3ac9
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity