← previous blocknext block →recent activity
Analyzing
Block #85,723,865
10 transactions · 9 stateful · 2026-07-05 08:24:34 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,723,865 · 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
0xb538d919…3283
0x065c9d…c394
4 touches
1 conflict
0xe6b19f9e…ad68
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfc1a1820…6377
0x065c9d…c394
4 touches
1 conflict
0x22668faf…039f
0x065c9d…c394
3 touches
1 conflict
0x34809dc8…bbdb
0x065c9d…c394
3 touches
1 conflict
0x3ef0dd5f…6df2
0x065c9d…c394
3 touches
1 conflict
0xdb63f6db…2b3f
0x065c9d…c394
3 touches
1 conflict
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 0xb538d919b3…243283
Audit this contract →
← previous block·next block →recent activity