← previous blocknext block →recent activity
Analyzing
Block #85,973,904
35 transactions · 25 stateful · 2026-07-06 12:10:08 UTC
Parallelism
89/100
Blocked
44%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,973,904 · 35 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
1w02w03w14w213w018w119w020w121w123w324w025w226w027w128w229w333w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xd92a03c7…bfc7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x9da6e429…074d
0xa6afd3…d132
6 touches
3 conflicts
0xb43dc900…22f2
0xa6afd3…d132
6 touches
3 conflicts
0x8551480c…c7fc
0xa6afd3…d132
5 touches
3 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: 0x40c49f17…d22af0
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity