← previous blocknext block →recent activity
Analyzing
Block #98,072,236
38 transactions · 36 stateful · 2026-08-22 02:21:41 UTC
Parallelism
74/100
Blocked
58%
Avg conflicts / tx
1.45
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #98,072,236 · 38 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w08w19w210w012w013w114w015w118w119w220w121w322w324w425w527w128w529w635w836w937w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca5b9231…3bd1
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xb575cf74…fbd5
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0x2c44ac3a…0195
0xd32edf…ff58
7 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: Perpl
10 conflicts on slot 0xca5b9231b2…f33bd1
Audit this contract →
← previous block·next block →recent activity