← previous blocknext block →recent activity
Analyzing
Block #98,524,040
20 transactions · 19 stateful · 2026-08-23 16:20:43 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,524,040 · 20 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
1w02w13w25w011w112w213w315w416w518w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xf77196fd…dbe1
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x022f65…485d
6 touches
3 conflicts
0x00000000…0002
0x022f65…485d
6 touches
3 conflicts
0x00000000…0003
0x022f65…485d
6 touches
3 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
6 touches
3 conflicts
0xbadf26c2…c505
0xe15503…7777
6 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity