← previous blocknext block →recent activity
Analyzing
Block #85,939,944
13 transactions · 8 stateful · 2026-07-06 08:23:36 UTC
Parallelism
85/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,939,944 · 13 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
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x21fe60fc…f481
0x065c9d…c394
2 touches
0 conflicts
0x2e318aa7…5d98
0x065c9d…c394
2 touches
0 conflicts
0x5cb8560f…2ff6
0x065c9d…c394
2 touches
0 conflicts
0x6192498f…477b
0x065c9d…c394
2 touches
0 conflicts
0xbfae9a5f…c625
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
1 conflict on slot 0x160f117d43…518e90
Audit this contract →
← previous block·next block →recent activity