← previous blocknext block →recent activity
Analyzing
Block #86,047,222
16 transactions · 12 stateful · 2026-07-06 20:20:08 UTC
Parallelism
81/100
Blocked
17%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,047,222 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x315f4372…08ca
0x065c9d…c394
2 touches
0 conflicts
0x40bedc5f…3039
0x065c9d…c394
2 touches
0 conflicts
0x614293af…bbb5
0x065c9d…c394
2 touches
0 conflicts
0xb833cc91…b726
0x065c9d…c394
2 touches
0 conflicts
0xd66e3b52…e260
0x065c9d…c394
2 touches
0 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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity