← previous blocknext block →recent activity
Analyzing
Block #85,760,115
11 transactions · 10 stateful · 2026-07-05 12:25:39 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,760,115 · 11 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64b06001…e222
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc2ad3c06…d9e1
0x065c9d…c394
3 touches
1 conflict
0x8af4e846…421f
0x065c9d…c394
3 touches
1 conflict
0xb47931ce…299a
0x065c9d…c394
2 touches
0 conflicts
0xc123643a…cacb
0x065c9d…c394
2 touches
0 conflicts
0xfc9da169…2fcc
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x64b0600140…a8e222
Audit this contract →
← previous block·next block →recent activity