← previous blocknext block →recent activity
Analyzing
Block #85,973,032
31 transactions · 22 stateful · 2026-07-06 12:04:18 UTC
Parallelism
87/100
Blocked
41%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,973,032 · 31 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
4w05w18w011w012w115w218w019w221w124w125w026w127w329w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0xb43dc900…22f2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x36fb57db…2181
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 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: 0x681e908b…e1ae09
6 conflicts on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity