← previous blocknext block →recent activity
Analyzing
Block #92,162,980
24 transactions · 23 stateful · 2026-08-01 09:10:38 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,162,980 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w210w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6576ad40…546e
0x7b9256…1fb2
8 touches
6 conflicts
0x3174f37b…a5f6
0x7b9256…1fb2
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x3174f37b…a5f3
0x7b9256…1fb2
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0x3174f37b…a5f2
0x7b9256…1fb2
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0x6576ad40…546f
0x7b9256…1fb2
8 touches
6 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
6 conflicts on slot 0x6576ad4015…95546e
Audit this contract →
← previous block·next block →recent activity