← previous blocknext block →recent activity
Analyzing
Block #92,065,260
20 transactions · 20 stateful · 2026-08-01 00:59:09 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,065,260 · 20 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
2w04w05w17w28w09w110w211w012w113w216w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9654d5ec…995b
0x7b9256…1fb2
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x441018a9…65db
0x7b9256…1fb2
6 touches
3 conflicts
0x441018a9…65dc
0x7b9256…1fb2
6 touches
3 conflicts
0x441018a9…65df
0x7b9256…1fb2
6 touches
3 conflicts
0x9654d5ec…995a
0x7b9256…1fb2
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
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: 0x7b9256fd…e21fb2
3 conflicts on slot 0x9654d5ec84…b6995b
Audit this contract →
← previous block·next block →recent activity