← previous blocknext block →recent activity
Analyzing
Block #85,565,021
9 transactions · 6 stateful · 2026-07-04 14:45:24 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,565,021 · 9 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2dc53ee8…7bf1
0x065c9d…c394
2 touches
0 conflicts
0x46cbb937…8ad7
0x065c9d…c394
2 touches
0 conflicts
0x4ae5bea3…ffe8
0x065c9d…c394
2 touches
0 conflicts
0xa174f91d…8097
0x065c9d…c394
2 touches
0 conflicts
0xa5a3f7bf…7a9b
0x065c9d…c394
2 touches
0 conflicts
0xbd0df907…e1ef
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity