← previous blocknext block →recent activity
Analyzing
Block #91,998,528
32 transactions · 28 stateful · 2026-07-31 19:23:31 UTC
Parallelism
81/100
Blocked
54%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,998,528 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w08w111w312w314w015w116w017w118w219w320w421w522w423w429w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe219cf61…502f
0x7b9256…1fb2
12 touches
15 conflicts
0x177211e2…1c2d
0x754704…b603
12 touches
15 conflicts
0xe1f61186…e2f8
0x754704…b603
12 touches
15 conflicts
0x00000000…0006
0x7b9256…1fb2
12 touches
15 conflicts
0x4c90da18…bfbc
0x7b9256…1fb2
12 touches
15 conflicts
0x4c90da18…bfbd
0x7b9256…1fb2
12 touches
15 conflicts
0x4c90da18…bfc0
0x7b9256…1fb2
12 touches
15 conflicts
0xe219cf61…502e
0x7b9256…1fb2
12 touches
15 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
15 conflicts on slot 0xe219cf610d…9f502f
Audit this contract →
← previous block·next block →recent activity