← previous blocknext block →recent activity
Analyzing
Block #99,953,275
22 transactions · 21 stateful · 2026-08-28 17:05:01 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,953,275 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w26w39w410w014w519w120w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc9fa93a…f523
0x34b655…2a6f
10 touches
10 conflicts
0xfdafaeb3…4b67
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x24bb46f7…3853
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x7204dbb2…d6d4
0x34b655…2a6f
6 touches
3 conflicts
0x932a9590…0b19
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0xcc9fa93abb…ddf523
Audit this contract →
← previous block·next block →recent activity