← previous blocknext block →recent activity
Analyzing
Block #99,475,722
19 transactions · 19 stateful · 2026-08-27 00:47:28 UTC
Parallelism
84/100
Blocked
26%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,475,722 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w16w07w09w114w215w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57a7cf46…25d0
0x34b655…2a6f
6 touches
3 conflicts
0xb1856468…e84f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcd93b2d2…30e6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xded7831c…3c4a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
3 conflicts on slot 0x57a7cf464f…ec25d0
Audit this contract →
← previous block·next block →recent activity