← previous blocknext block →recent activity
Analyzing
Block #100,023,669
14 transactions · 14 stateful · 2026-08-28 22:59:32 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,023,669 · 14 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
6w07w19w210w311w412w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31827e57…3bb5
0x34b655…2a6f
8 touches
6 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
6 touches
3 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
6 touches
3 conflicts
0x4f46a4fb…3224
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
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
6 conflicts on slot 0x31827e577d…483bb5
Audit this contract →
← previous block·next block →recent activity