← previous blocknext block →recent activity
Analyzing
Block #97,186,906
16 transactions · 16 stateful · 2026-08-18 23:07:54 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,186,906 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w08w19w210w311w412w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34b1e500…7687
0x754704…b603
10 touches
10 conflicts
0xe0659a3f…90d9
0x000000…a032
10 touches
10 conflicts
0x00000000…000b
0x754704…b603
10 touches
10 conflicts
0x00000000…000b
0x78999c…f371
10 touches
10 conflicts
0x00000000…000f
0x78999c…f371
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
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: USDC (USDC)
10 conflicts on slot 0x34b1e500ac…197687
Audit this contract →
← previous block·next block →recent activity