← previous blocknext block →recent activity
Analyzing
Block #86,351,609
10 transactions · 10 stateful · 2026-07-08 06:12:01 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,351,609 · 10 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
1w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf04679eb…15d4
0x065c9d…c394
3 touches
1 conflict
0xd619a83f…9275
0x065c9d…c394
3 touches
1 conflict
0x148dc457…e120
0x065c9d…c394
2 touches
0 conflicts
0x27a04273…27c5
0x065c9d…c394
2 touches
0 conflicts
0x835690b0…3ff5
0x065c9d…c394
2 touches
0 conflicts
0x88711972…25a7
0x065c9d…c394
2 touches
0 conflicts
0x90032d0e…0988
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