← previous blocknext block →recent activity
Analyzing
Block #86,813,817
25 transactions · 24 stateful · 2026-07-10 09:42:59 UTC
Parallelism
72/100
Blocked
42%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,813,817 · 25 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
1w03w16w07w18w29w310w411w512w621w422w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
12 touches
15 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
12 touches
15 conflicts
0x4fe95978…4ea7
0x34b655…2a6f
12 touches
15 conflicts
0x63c900f4…2600
0x34b655…2a6f
12 touches
15 conflicts
0x9966da31…0d0f
0x34b655…2a6f
12 touches
15 conflicts
0x9f40a209…1193
0x34b655…2a6f
12 touches
15 conflicts
0xf7e59d30…11dd
0x34b655…2a6f
12 touches
15 conflicts
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity