← previous blocknext block →recent activity
Analyzing
Block #92,078,384
16 transactions · 16 stateful · 2026-08-01 02:05:09 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,078,384 · 16 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
2w03w14w07w08w19w210w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1b52e91…bb8b
0x7b9256…1fb2
8 touches
6 conflicts
0xc1b52e91…bb8c
0x7b9256…1fb2
8 touches
6 conflicts
0xc1b52e91…bb8f
0x7b9256…1fb2
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0x770b2225…e6ac
0x7b9256…1fb2
8 touches
6 conflicts
0x770b2225…e6ad
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 0xc1b52e91ff…d6bb8b
Audit this contract →
← previous block·next block →recent activity