← previous blocknext block →recent activity
Analyzing
Block #85,846,478
11 transactions · 11 stateful · 2026-07-05 22:00:52 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,846,478 · 11 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
1w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x013bbf61…898a
0x065c9d…c394
2 touches
0 conflicts
0x04483d24…b226
0x065c9d…c394
2 touches
0 conflicts
0x28f0fb54…4f36
0x065c9d…c394
2 touches
0 conflicts
0x517b1063…99cd
0x065c9d…c394
2 touches
0 conflicts
0xe8af79f5…94ea
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity