← previous blocknext block →recent activity
Analyzing
Block #85,962,956
17 transactions · 15 stateful · 2026-07-06 10:57:09 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,962,956 · 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
1w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0x1e46e258…023a
0x065c9d…c394
2 touches
0 conflicts
0x6076397e…114c
0x065c9d…c394
2 touches
0 conflicts
0x61745332…e032
0x065c9d…c394
2 touches
0 conflicts
0xc05ea88a…955f
0x065c9d…c394
2 touches
0 conflicts
0xd515dd4c…28f0
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity