← previous blocknext block →recent activity
Analyzing
Block #86,664,506
18 transactions · 15 stateful · 2026-07-09 17:05:54 UTC
Parallelism
61/100
Blocked
40%
Avg conflicts / tx
0.72
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,664,506 · 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
4w05w16w29w310w011w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa29182a1…c12c
0x34b655…2a6f
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x4293a398…286f
0x34b655…2a6f
4 touches
1 conflict
0x6c7e1952…d9c9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x79ad9283…5fd1
0x34b655…2a6f
4 touches
1 conflict
0x7b6c252d…a696
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 0xa29182a19c…86c12c
Audit this contract →
← previous block·next block →recent activity