← previous blocknext block →recent activity
Analyzing
Block #86,511,832
21 transactions · 19 stateful · 2026-07-09 00:02:38 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,511,832 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8388eab6…83ff
0x34b655…2a6f
16 touches
28 conflicts
0xf6c9690b…cc0b
0x34b655…2a6f
16 touches
28 conflicts
0x9c449f77…6992
0x34b655…2a6f
16 touches
28 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 conflicts
0x63c900f4…2600
0x34b655…2a6f
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
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
28 conflicts on slot 0x8388eab63f…1e83ff
Audit this contract →
← previous block·next block →recent activity