← previous blocknext block →recent activity
Analyzing
Block #86,340,579
16 transactions · 12 stateful · 2026-07-08 04:58:26 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,340,579 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x0f3d78ee…6e21
0x065c9d…c394
2 touches
0 conflicts
0x28ba3f97…21e4
0x065c9d…c394
2 touches
0 conflicts
0x56bf0a3e…d2a3
0x065c9d…c394
2 touches
0 conflicts
0x893269ed…c47f
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
1 conflict on slot 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity