← previous blocknext block →recent activity
Analyzing
Block #99,211,522
18 transactions · 16 stateful · 2026-08-26 02:37:32 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,211,522 · 18 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
1w02w13w24w05w18w09w011w112w113w214w315w417w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2d8af24…4750
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x76622fb2…4f08
0x34b655…2a6f
6 touches
3 conflicts
0xebc19198…4402
0xd32edf…ff58
5 touches
3 conflicts
0xba5743c7…21c2
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x07c2e48b…3c16
0x34b655…2a6f
4 touches
1 conflict
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 0xb2d8af2470…774750
Audit this contract →
← previous block·next block →recent activity