← previous blocknext block →recent activity
Analyzing
Block #99,171,199
21 transactions · 19 stateful · 2026-08-25 23:14:40 UTC
Parallelism
76/100
Blocked
58%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,171,199 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w18w29w110w212w315w318w419w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xd1203697…1ae0
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x2057be7e…4cde
0x40c49f…2af0
4 touches
1 conflict
0xa57334d4…ee07
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe3684e08…c96a
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity