← previous blocknext block →recent activity
Analyzing
Block #86,328,012
20 transactions · 18 stateful · 2026-07-08 03:34:30 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,328,012 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w012w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0xb8d914cc…1f1f
0x065c9d…c394
4 touches
1 conflict
0xfb5f6352…630b
0x065c9d…c394
3 touches
1 conflict
0xad18ed19…4c7e
0x065c9d…c394
3 touches
1 conflict
0x26e1fda0…2ba4
0x065c9d…c394
3 touches
1 conflict
0x9dd0a735…4d04
0x34b655…2a6f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity