← previous blocknext block →recent activity
Analyzing
Block #99,658,755
20 transactions · 19 stateful · 2026-08-27 16:16:02 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
0.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,658,755 · 20 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
1w02w13w24w210w311w414w515w618w019w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
6 touches
3 conflicts
0x6c6f37ba…c209
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
3 conflicts on slot 0x629109215a…273016
Audit this contract →
← previous block·next block →recent activity