← previous blocknext block →recent activity
Analyzing
Block #85,919,404
35 transactions · 31 stateful · 2026-07-06 06:06:36 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
2.71
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #85,919,404 · 35 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w39w410w511w613w714w815w916w1017w1118w1219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
26 touches
78 conflicts
0xfa2b4f19…a18f
0xd32edf…ff58
9 touches
10 conflicts
0xafd867b7…2b2e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xae9dcc34…681c
0x34b655…2a6f
6 touches
3 conflicts
0xafd867b7…2b2d
0x34b655…2a6f
6 touches
3 conflicts
0x69017fce…85bc
0x1b6862…e19c
4 touches
1 conflict
0x482471ad…122f
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
78 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity