← previous blocknext block →recent activity
Analyzing
Block #85,913,946
12 transactions · 10 stateful · 2026-07-06 05:30:16 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,913,946 · 12 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
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x48ca6006…e4a6
0x065c9d…c394
3 touches
1 conflict
0x70ddb21a…a115
0x065c9d…c394
3 touches
1 conflict
0x15d8a102…055d
0x065c9d…c394
3 touches
1 conflict
0x07843493…d304
0x065c9d…c394
3 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0x19b23367…08bf
0x34b655…2a6f
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 0xb33ff82315…a81188
Audit this contract →
← previous block·next block →recent activity