← previous blocknext block →recent activity
Analyzing
Block #99,208,580
18 transactions · 14 stateful · 2026-08-26 02:22:44 UTC
Parallelism
83/100
Blocked
21%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,208,580 · 18 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
2w04w07w111w116w017w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x554873fd…2ff4
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xb2b8c7ba…6463
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc8ab31f9…8ce9
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xa366dc41…b2d8
0xa6afd3…d132
4 touches
1 conflict
0x7aad02c6…b979
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 0x554873fdcf…d42ff4
Audit this contract →
← previous block·next block →recent activity