← previous blocknext block →recent activity
Analyzing
Block #98,443,606
22 transactions · 18 stateful · 2026-08-23 09:30:49 UTC
Parallelism
73/100
Blocked
39%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,443,606 · 22 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
1w02w16w08w09w110w211w315w416w517w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ddc4a77…765e
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x79aa79ed…2554
0x34b655…2a6f
8 touches
6 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xcfac6a2a…37f5
0x34b655…2a6f
5 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
5 touches
3 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
15 conflicts on slot 0x5ddc4a7765…4b765e
Audit this contract →
← previous block·next block →recent activity