← previous blocknext block →recent activity
Analyzing
Block #92,769,777
14 transactions · 13 stateful · 2026-08-03 12:03:37 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,769,777 · 14 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
1w02w03w14w27w08w211w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64a785e4…0110
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x0395f77a…39bb
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x56fed0dd…581f
0x34b655…2a6f
4 touches
1 conflict
0x56fed0dd…5820
0x34b655…2a6f
4 touches
1 conflict
0x76c4467d…ce28
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 0x64a785e491…1c0110
Audit this contract →
← previous block·next block →recent activity