← previous blocknext block →recent activity
Analyzing
Block #99,935,428
16 transactions · 16 stateful · 2026-08-28 15:35:03 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,935,428 · 16 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
2w03w04w15w06w19w010w011w213w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9868b52…c77f
0x34b655…2a6f
6 touches
3 conflicts
0x9c168b41…7486
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd119dfce…907d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3ad04ce1…1904
0xa6afd3…d132
4 touches
1 conflict
0xdb40334f…e0bc
0xa6afd3…d132
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 0xb9868b5233…c6c77f
Audit this contract →
← previous block·next block →recent activity