← previous blocknext block →recent activity
Analyzing
Block #92,005,965
22 transactions · 22 stateful · 2026-07-31 20:00:55 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,005,965 · 22 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
1w02w13w25w06w18w011w312w113w414w216w318w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x342fbbca…d443
0x40c49f…2af0
8 touches
6 conflicts
0x3de775b2…319b
0xa6afd3…d132
8 touches
6 conflicts
0xfa551be3…a911
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0x1a287886…0266
0xa6afd3…d132
6 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
6 conflicts on slot 0x342fbbca09…fcd443
Audit this contract →
← previous block·next block →recent activity