← previous blocknext block →recent activity
Analyzing
Block #86,700,967
16 transactions · 14 stateful · 2026-07-09 21:09:13 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,700,967 · 16 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
2w03w16w07w18w210w311w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x4b2b1640…1bb8
0x34b655…2a6f
8 touches
6 conflicts
0xd1952ceb…56be
0x34b655…2a6f
6 touches
3 conflicts
0xd53275f1…0a33
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x68ae6fca…0224
0x34b655…2a6f
4 touches
1 conflict
0x816c7d6d…98ea
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity