← previous blocknext block →recent activity
Analyzing
Block #98,654,725
34 transactions · 29 stateful · 2026-08-24 03:41:37 UTC
Parallelism
68/100
Blocked
62%
Avg conflicts / tx
1.74
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #98,654,725 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w08w110w011w113w214w315w418w521w622w723w824w925w1027w131w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x11b69a7e…334e
0xee8c0e…1242
12 touches
15 conflicts
0x891821c5…10c9
0xd32edf…ff58
11 touches
15 conflicts
0x58e06bab…34d2
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity