← previous blocknext block →recent activity
Analyzing
Block #100,704,972
38 transactions · 32 stateful · 2026-08-31 08:11:43 UTC
Parallelism
74/100
Blocked
59%
Avg conflicts / tx
1.47
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,704,972 · 38 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w212w413w514w618w421w722w825w327w436w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23529e13…6f25
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x228af835…b233
0xd32edf…ff58
9 touches
10 conflicts
0x01f72dfa…3d18
0x34b655…2a6f
8 touches
6 conflicts
0xba5743c7…21bf
0x1b6862…e19c
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xd78d92d4…d5ed
0x065c9d…c394
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
21 conflicts on slot 0x23529e136b…8a6f25
Audit this contract →
← previous block·next block →recent activity