← previous blocknext block →recent activity
Analyzing
Block #85,505,096
10 transactions · 8 stateful · 2026-07-04 08:06:23 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,505,096 · 10 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbb7c40e1…e767
0x065c9d…c394
4 touches
1 conflict
0x4f638b72…db39
0x065c9d…c394
3 touches
1 conflict
0xc530cac9…91e1
0x065c9d…c394
3 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
2 touches
0 conflicts
0x2f6af1db…121e
0x065c9d…c394
2 touches
0 conflicts
0x4a7e91bb…d690
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