← previous blocknext block →recent activity
Analyzing
Block #86,531,498
18 transactions · 16 stateful · 2026-07-09 02:13:58 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,531,498 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w013w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x44eb5a33…a2d5
0x34b655…2a6f
6 touches
3 conflicts
0x334649c0…069e
0x34b655…2a6f
4 touches
1 conflict
0x398521f2…af79
0x34b655…2a6f
4 touches
1 conflict
0x3f24a374…6bc3
0x34b655…2a6f
4 touches
1 conflict
0xf9150155…e080
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0xdba422af…42ec
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity