← previous blocknext block →recent activity
Analyzing
Block #85,741,903
9 transactions · 9 stateful · 2026-07-05 10:24:29 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,741,903 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x35f470c6…d7c0
0x065c9d…c394
4 touches
1 conflict
0x02194ee7…9f86
0x065c9d…c394
3 touches
1 conflict
0xd56ce329…6271
0x065c9d…c394
3 touches
1 conflict
0xf741ffee…ee61
0x065c9d…c394
3 touches
1 conflict
0xfa9edeef…803f
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 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity