← previous blocknext block →recent activity
Analyzing
Block #99,076,965
90 transactions · 90 stateful · 2026-08-25 15:20:09 UTC
Parallelism
97/100
Blocked
9%
Avg conflicts / tx
0.11
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,076,965 · 90 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
2w03w14w26w07w18w09w113w184w287w088w189w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb55f6c75…c2d2
0xa6afd3…d132
4 touches
1 conflict
0xded216ce…191a
0xa6afd3…d132
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity