← previous blocknext block →recent activity
Analyzing
Block #85,643,169
13 transactions · 11 stateful · 2026-07-04 23:25:41 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,643,169 · 13 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf90ebe0…64a9
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x422f43d9…32e9
0x065c9d…c394
3 touches
1 conflict
0xeca56535…e0bb
0x065c9d…c394
3 touches
1 conflict
0x5fc5263b…57a1
0x065c9d…c394
2 touches
0 conflicts
0x61ea7e26…222d
0x065c9d…c394
2 touches
0 conflicts
0x660dd3f1…6bcc
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
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 0xaf90ebe0b5…4f64a9
Audit this contract →
← previous block·next block →recent activity