← previous blocknext block →recent activity
Analyzing
Block #100,981,597
15 transactions · 14 stateful · 2026-09-01 07:23:38 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,981,597 · 15 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
1w06w07w18w212w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x165d6ec5…b2d2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
6 touches
3 conflicts
0xae7853a9…4e05
0x34b655…2a6f
5 touches
3 conflicts
0x68eafe1d…6d1b
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x08be6a43…f4dc
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 0x165d6ec5bf…f1b2d2
Audit this contract →
← previous block·next block →recent activity