← previous blocknext block →recent activity
Analyzing
Block #98,286,266
25 transactions · 25 stateful · 2026-08-22 20:19:12 UTC
Parallelism
64/100
Blocked
60%
Avg conflicts / tx
1.36
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #98,286,266 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w28w19w010w111w215w316w317w419w420w521w622w723w824w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5ff384c…3a25
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x91945265…e58b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
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
10 conflicts on slot 0xa5ff384ced…053a25
Audit this contract →
← previous block·next block →recent activity