← previous blocknext block →recent activity
Analyzing
Block #100,603,754
25 transactions · 23 stateful · 2026-08-30 23:42:34 UTC
Parallelism
64/100
Blocked
61%
Avg conflicts / tx
1.56
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,603,754 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w17w28w310w412w416w417w518w619w120w223w724w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd1306ad…f1b8
0x34b655…2a6f
10 touches
10 conflicts
0xeca74ff3…a361
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf12a8246…e00f
0xa6afd3…d132
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 0xcd1306adf3…44f1b8
Audit this contract →
← previous block·next block →recent activity