← previous blocknext block →recent activity
Analyzing
Block #85,764,043
7 transactions · 6 stateful · 2026-07-05 12:51:45 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,764,043 · 7 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
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2dbc6c37…16dc
0x065c9d…c394
2 touches
0 conflicts
0x58e54f25…6997
0x065c9d…c394
2 touches
0 conflicts
0x75077d31…cb58
0x065c9d…c394
2 touches
0 conflicts
0xda8a8d40…8903
0x065c9d…c394
2 touches
0 conflicts
0xef1d9c1a…3ac4
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity