← previous blocknext block →recent activity
Analyzing
Block #92,765,220
13 transactions · 13 stateful · 2026-08-03 11:40:42 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,765,220 · 13 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
2w03w04w15w210w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x624a8689…c9a9
0x34b655…2a6f
6 touches
3 conflicts
0xe5a9274d…78d7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x08a39015…efa0
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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: Perpl
3 conflicts on slot 0x624a868974…80c9a9
Audit this contract →
← previous block·next block →recent activity