← previous blocknext block →recent activity
Analyzing
Block #98,080,972
24 transactions · 21 stateful · 2026-08-22 03:05:39 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,080,972 · 24 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
1w02w13w24w06w08w010w111w312w413w214w317w418w521w523w1
- 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
12 touches
15 conflicts
0xd5df7463…178c
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x2ce2d49e…d189
0x1b6862…e19c
8 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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity