← previous blocknext block →recent activity
Analyzing
Block #86,669,940
26 transactions · 25 stateful · 2026-07-09 17:42:09 UTC
Parallelism
58/100
Blocked
52%
Avg conflicts / tx
1.69
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,669,940 · 26 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w711w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0x025393f0…8bab
0x34b655…2a6f
16 touches
28 conflicts
0x727fbce7…0c80
0x34b655…2a6f
16 touches
28 conflicts
0xb25fa8e2…c9ef
0x34b655…2a6f
16 touches
28 conflicts
0xf58f4849…c7c7
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity