← previous blocknext block →recent activity
Analyzing
Block #85,969,277
14 transactions · 11 stateful · 2026-07-06 11:39:15 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,969,277 · 14 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
1w03w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x5724cb94…a3c7
0x065c9d…c394
4 touches
1 conflict
0x6714395e…e133
0x065c9d…c394
3 touches
1 conflict
0x706a6e9f…600a
0x065c9d…c394
3 touches
1 conflict
0xd519f276…aa62
0x0555e3…2b9c
2 touches
0 conflicts
0x4d037ed1…a770
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x094452…0a09
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