← previous blocknext block →recent activity
Analyzing
Block #98,390,507
30 transactions · 25 stateful · 2026-08-23 05:03:41 UTC
Parallelism
83/100
Blocked
64%
Avg conflicts / tx
1.3
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,390,507 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w39w410w011w112w213w315w121w422w224w425w326w428w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x47c6a28b…e943
0xd32edf…ff58
9 touches
10 conflicts
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xb99398a0…919f
0x34b655…2a6f
8 touches
6 conflicts
0xc2aacf41…54ff
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity