← previous blocknext block →recent activity
Analyzing
Block #99,618,199
21 transactions · 21 stateful · 2026-08-27 12:51:04 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,618,199 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w16w07w18w012w213w314w415w518w019w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fce7a05…d778
0x34b655…2a6f
12 touches
15 conflicts
0x57da6699…04b0
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xd53220ed…4737
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xb4614acc…47d7
0x34b655…2a6f
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
15 conflicts on slot 0x6fce7a0516…35d778
Audit this contract →
← previous block·next block →recent activity