← previous blocknext block →recent activity
Analyzing
Block #85,992,904
25 transactions · 19 stateful · 2026-07-06 14:17:11 UTC
Parallelism
84/100
Blocked
16%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,992,904 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x23c2d156…4d31
0x065c9d…c394
2 touches
0 conflicts
0x81c2febc…2231
0x065c9d…c394
2 touches
0 conflicts
0x9a45cfe1…8a80
0x065c9d…c394
2 touches
0 conflicts
0xd3218460…609b
0x065c9d…c394
2 touches
0 conflicts
0xda36c81c…a2e4
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity