← previous blocknext block →recent activity
Analyzing
Block #85,366,212
17 transactions · 16 stateful · 2026-07-03 16:41:42 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,366,212 · 17 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
1w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbd197a40…2c24
0x065c9d…c394
4 touches
1 conflict
0x5b6f8118…d31d
0x065c9d…c394
4 touches
1 conflict
0x7bbddfaa…358b
0x065c9d…c394
3 touches
1 conflict
0x2db93d48…2cc6
0x065c9d…c394
2 touches
0 conflicts
0x60c06c4b…fab8
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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