← previous blocknext block →recent activity
Analyzing
Block #98,674,263
55 transactions · 53 stateful · 2026-08-24 05:23:30 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1.64
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #98,674,263 · 55 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
1w02w13w04w06w07w18w210w012w113w214w315w016w017w118w224w126w227w330w435w236w139w440w549w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f1
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x2270ec44…6c95
0xd32edf…ff58
9 touches
10 conflicts
0x6d1b72ee…6b78
0x34b655…2a6f
8 touches
6 conflicts
0x81ceb686…4df3
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
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
10 conflicts on slot 0x9a3068dd84…9918f1
Audit this contract →
← previous block·next block →recent activity