← previous blocknext block →recent activity
Analyzing
Block #100,615,622
22 transactions · 21 stateful · 2026-08-31 00:42:17 UTC
Parallelism
77/100
Blocked
43%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,615,622 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w07w19w210w111w212w013w114w315w418w120w021w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4080da5f…c128
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1e168c8b…6945
0x34b655…2a6f
6 touches
3 conflicts
0x25ed265f…63b4
0x34b655…2a6f
6 touches
3 conflicts
0x0476d77b…a514
0x34b655…2a6f
6 touches
3 conflicts
0xafb22303…6db2
0x34b655…2a6f
4 touches
1 conflict
0xb5fafd44…cd1b
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
10 conflicts on slot 0x4080da5ff3…95c128
Audit this contract →
← previous block·next block →recent activity