← previous blocknext block →recent activity
Analyzing
Block #86,924,343
22 transactions · 20 stateful · 2026-07-10 22:02:08 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,924,343 · 22 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
5w06w17w28w310w413w514w519w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa08f40b2…9a93
0x34b655…2a6f
14 touches
21 conflicts
0xa248a5dd…4a69
0x34b655…2a6f
10 touches
10 conflicts
0x3a996b35…bc8f
0x34b655…2a6f
8 touches
6 conflicts
0x493b81c1…688d
0x34b655…2a6f
8 touches
6 conflicts
0x041ecdd0…6228
0x34b655…2a6f
8 touches
6 conflicts
0x0d43cc69…6f83
0x34b655…2a6f
8 touches
6 conflicts
0x6e90b9b1…dca8
0x34b655…2a6f
8 touches
6 conflicts
0xe246730f…760d
0x34b655…2a6f
8 touches
6 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 0xa08f40b255…099a93
Audit this contract →
← previous block·next block →recent activity