← previous blocknext block →recent activity
Analyzing
Block #85,171,058
25 transactions · 24 stateful · 2026-07-02 19:01:40 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,171,058 · 25 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
8w011w013w117w118w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd4f60bce…e7f9
0x34b655…2a6f
4 touches
1 conflict
0xdeddb1c8…0d40
0x34b655…2a6f
4 touches
1 conflict
0x2a62cf79…8853
0x065c9d…c394
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x577b2428…6cab
0x3c2269…cf62
2 touches
0 conflicts
0x5b3b7d9f…fa52
0x3c2269…cf62
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity