← previous blocknext block →recent activity
Analyzing
Block #99,476,217
17 transactions · 14 stateful · 2026-08-27 00:49:57 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,476,217 · 17 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
4w06w07w18w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a100e05…c541
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xdd6538fb…2b3f
0x34b655…2a6f
4 touches
1 conflict
0xfe96ad50…3aa3
0x34b655…2a6f
4 touches
1 conflict
0x2202504e…fad0
0x34b655…2a6f
2 touches
0 conflicts
0x4c410cdc…96bb
0x34b655…2a6f
2 touches
0 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 0x9a100e057a…2ac541
Audit this contract →
← previous block·next block →recent activity