← previous blocknext block →recent activity
Analyzing
Block #85,967,319
12 transactions · 10 stateful · 2026-07-06 11:26:14 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,967,319 · 12 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
1w02w13w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x5d291891…e374
0x065c9d…c394
3 touches
1 conflict
0x93f40757…4da5
0x065c9d…c394
3 touches
1 conflict
0xc942f218…1556
0x40c49f…2af0
2 touches
0 conflicts
0xd8df816d…66ab
0x40c49f…2af0
2 touches
0 conflicts
0xfaf784db…bb36
0x40c49f…2af0
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