← previous blocknext block →recent activity
Analyzing
Block #85,504,399
11 transactions · 10 stateful · 2026-07-04 08:01:46 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,504,399 · 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
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe80d5668…909b
0x065c9d…c394
4 touches
1 conflict
0x395afa9a…21c1
0x065c9d…c394
3 touches
1 conflict
0xad2d4960…21e1
0x065c9d…c394
3 touches
1 conflict
0x3d796fac…96d7
0x065c9d…c394
2 touches
0 conflicts
0x5a330c21…21dd
0x065c9d…c394
2 touches
0 conflicts
0x7067a58d…e02e
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
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