← previous blocknext block →recent activity
Analyzing
Block #86,963,251
26 transactions · 23 stateful · 2026-07-11 02:22:05 UTC
Parallelism
77/100
Blocked
39%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,963,251 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w010w111w213w316w417w519w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xb652c396…b8fa
0x34b655…2a6f
6 touches
3 conflicts
0x3bffe642…cff3
0x34b655…2a6f
6 touches
3 conflicts
0xa0237ed3…2622
0x34b655…2a6f
6 touches
3 conflicts
0x796488e2…ee71
0x34b655…2a6f
6 touches
3 conflicts
0x796488e2…ee72
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity