← previous blocknext block →recent activity
Analyzing
Block #85,853,909
42 transactions · 29 stateful · 2026-07-05 22:50:27 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,853,909 · 42 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w07w18w111w012w113w217w218w019w123w324w425w026w140w141w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0x6f70178a…8532
0xd32edf…ff58
5 touches
3 conflicts
0x44ad89ba…cf83
0x0a917f…7777
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
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: 0x04fdeac2…f747d7
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity