← previous blocknext block →recent activity
Analyzing
Block #99,478,052
21 transactions · 19 stateful · 2026-08-27 00:59:11 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,478,052 · 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
1w02w13w04w16w07w18w19w211w115w216w317w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e698c15…d3c5
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
0x34b655…2a6f
6 touches
3 conflicts
0xf38a3927…ad62
0x34b655…2a6f
6 touches
3 conflicts
0x1f8a126c…9aa1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0x1e698c1576…56d3c5
Audit this contract →
← previous block·next block →recent activity