← previous blocknext block →recent activity
Analyzing
Block #85,967,995
21 transactions · 16 stateful · 2026-07-06 11:30:42 UTC
Parallelism
86/100
Blocked
19%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,967,995 · 21 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
2w04w08w010w111w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf08b155f…c913
0x065c9d…c394
4 touches
1 conflict
0xf54de2c5…482a
0xd32edf…ff58
3 touches
1 conflict
0x7ac2975d…f5eb
0x065c9d…c394
3 touches
1 conflict
0xa30c52c4…358d
0x065c9d…c394
3 touches
1 conflict
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