← previous blocknext block →recent activity
Analyzing
Block #85,568,724
24 transactions · 16 stateful · 2026-07-04 15:09:58 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,568,724 · 24 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
1w02w13w06w07w18w214w218w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0f77bf68…c8db
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6105c826…20d3
0x065c9d…c394
4 touches
1 conflict
0xadd807da…f30e
0x065c9d…c394
3 touches
1 conflict
0x1c644686…4a60
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: 0x04fdeac2…f747d7
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity