← previous blocknext block →recent activity
Analyzing
Block #92,433,240
12 transactions · 11 stateful · 2026-08-02 07:49:46 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,433,240 · 12 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
4w05w16w07w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee50bd58…f2fd
0x7b9256…1fb2
6 touches
3 conflicts
0xee50bd58…f2fe
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x84f8a6c1…f7f8
0x7b9256…1fb2
6 touches
3 conflicts
0x84f8a6c1…f7f9
0x7b9256…1fb2
6 touches
3 conflicts
0x84f8a6c1…f7fc
0x7b9256…1fb2
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 0xee50bd583c…c9f2fd
Audit this contract →
← previous block·next block →recent activity