← previous blocknext block →recent activity
Analyzing
Block #100,614,169
21 transactions · 20 stateful · 2026-08-31 00:34:58 UTC
Parallelism
81/100
Blocked
30%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,614,169 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w07w111w212w213w315w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e168c8b…6945
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd25f77bc…c191
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0476d77b…a514
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x1e168c8bca…f56945
Audit this contract →
← previous block·next block →recent activity