← previous blocknext block →recent activity
Analyzing
Block #85,765,543
20 transactions · 19 stateful · 2026-07-05 13:01:45 UTC
Parallelism
90/100
Blocked
5%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,765,543 · 20 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
1w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19f40fdd…c416
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x6e698bd1…0487
0x065c9d…c394
2 touches
0 conflicts
0x8cb5fbf3…5d5e
0x065c9d…c394
2 touches
0 conflicts
0xcaae9361…0d84
0x065c9d…c394
2 touches
0 conflicts
0xda8a8d40…8903
0x065c9d…c394
2 touches
0 conflicts
0xf861d86f…3dbc
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 0x19f40fdd5d…adc416
Audit this contract →
← previous block·next block →recent activity