← previous blocknext block →recent activity
Analyzing
Block #86,663,353
18 transactions · 16 stateful · 2026-07-09 16:58:11 UTC
Parallelism
61/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,663,353 · 18 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
3w04w16w27w38w411w015w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x899723a2…657b
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb652c396…b8fa
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6c68ddc9…d106
0xb1dbf0…c0d3
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
3 conflicts on slot 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity