← previous blocknext block →recent activity
Analyzing
Block #98,848,354
36 transactions · 28 stateful · 2026-08-24 20:03:42 UTC
Parallelism
81/100
Blocked
57%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,848,354 · 36 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
1w02w13w24w311w012w413w214w315w016w117w318w423w426w327w528w629w133w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41be9e75…9773
0x34b655…2a6f
8 touches
6 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x58e06bab…34ce
0x1b6862…e19c
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
6 conflicts on slot 0x41be9e7517…b39773
Audit this contract →
← previous block·next block →recent activity