← previous blocknext block →recent activity
Analyzing
Block #86,769,831
20 transactions · 18 stateful · 2026-07-10 04:49:19 UTC
Parallelism
85/100
Blocked
28%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,769,831 · 20 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
3w05w06w18w09w111w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x26054cbe…47df
0x34b655…2a6f
4 touches
1 conflict
0x313d3d93…4aa2
0x34b655…2a6f
4 touches
1 conflict
0x3e6563f1…1c23
0x34b655…2a6f
4 touches
1 conflict
0x4293a398…286e
0x34b655…2a6f
4 touches
1 conflict
0x4293a398…286f
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity