← previous blocknext block →recent activity
Analyzing
Block #86,316,264
12 transactions · 10 stateful · 2026-07-08 02:16:01 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,316,264 · 12 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
1w05w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x459573ed…fbbe
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0ddd94b1…7f23
0x065c9d…c394
2 touches
0 conflicts
0x2b235d67…9ecb
0x065c9d…c394
2 touches
0 conflicts
0x79851180…a367
0x065c9d…c394
2 touches
0 conflicts
0xc3fa28bc…7170
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 0x27a04273d4…7327c5
Audit this contract →
← previous block·next block →recent activity