← previous blocknext block →recent activity
Analyzing
Block #92,431,852
15 transactions · 15 stateful · 2026-08-02 07:42:48 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,431,852 · 15 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
2w03w14w25w06w17w29w310w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8f25135…4897
0x7b9256…1fb2
8 touches
6 conflicts
0xa8f25135…4894
0x7b9256…1fb2
8 touches
6 conflicts
0xa8f25135…4893
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
0xe2a5d6e7…d821
0x7b9256…1fb2
8 touches
6 conflicts
0xe2a5d6e7…d820
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 0xa8f25135e3…034897
Audit this contract →
← previous block·next block →recent activity