← previous blocknext block →recent activity
Analyzing
Block #85,959,254
28 transactions · 19 stateful · 2026-07-06 10:32:22 UTC
Parallelism
89/100
Blocked
32%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,959,254 · 28 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
1w02w13w06w08w09w110w211w112w215w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0x29f7e8dc…84d3
0x40c49f…2af0
6 touches
3 conflicts
0x342fbbca…d443
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x66f473d3…2d03
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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: 0x40c49f17…d22af0
3 conflicts on slot 0xffa7d0a419…63b10a
Audit this contract →
← previous block·next block →recent activity