← previous blocknext block →recent activity
Analyzing
Block #99,198,929
38 transactions · 34 stateful · 2026-08-26 01:34:12 UTC
Parallelism
82/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,198,929 · 38 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w010w311w013w014w118w019w120w222w124w425w528w629w234w336w537w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9659d1ee…317c
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x394c3833…b4a9
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
6 conflicts on slot 0x9659d1ee43…96317c
Audit this contract →
← previous block·next block →recent activity