← previous blocknext block →recent activity
Analyzing
Block #85,781,033
21 transactions · 9 stateful · 2026-07-05 14:44:51 UTC
Parallelism
90/100
Blocked
11%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,781,033 · 21 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x047f86bc…d6a6
0x065c9d…c394
2 touches
0 conflicts
0x1fbae59b…c10f
0x065c9d…c394
2 touches
0 conflicts
0x6d67f4a5…06d0
0x065c9d…c394
2 touches
0 conflicts
0x8c9c28de…dbd4
0x065c9d…c394
2 touches
0 conflicts
0x91393c4f…25b4
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity