← previous blocknext block →recent activity
Analyzing
Block #85,929,104
19 transactions · 16 stateful · 2026-07-06 07:11:15 UTC
Parallelism
84/100
Blocked
19%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,929,104 · 19 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
1w03w04w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x41b62f12…a1b1
0x065c9d…c394
4 touches
1 conflict
0x3246eb65…c06e
0x065c9d…c394
3 touches
1 conflict
0x54a5ab71…fee8
0x065c9d…c394
3 touches
1 conflict
0x9d4fdff0…b43a
0x065c9d…c394
3 touches
1 conflict
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 0x160f117d43…518e90
Audit this contract →
← previous block·next block →recent activity