← previous blocknext block →recent activity
Analyzing
Block #99,368,591
20 transactions · 19 stateful · 2026-08-26 15:48:05 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,368,591 · 20 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
3w04w15w06w27w310w413w014w115w517w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfb4fd6ce…262e
0x34b655…2a6f
4 touches
1 conflict
0x7ea1cfdf…81c0
0xa6afd3…d132
4 touches
1 conflict
0x025767ce…c2f3
0x34b655…2a6f
4 touches
1 conflict
0xb26ff3de…9352
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity