← previous blocknext block →recent activity
Analyzing
Block #100,629,154
26 transactions · 23 stateful · 2026-08-31 01:50:21 UTC
Parallelism
65/100
Blocked
52%
Avg conflicts / tx
0.88
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,629,154 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w28w09w112w313w414w517w618w720w021w122w125w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb482658a…e4f5
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb240b520…a88a
0x34b655…2a6f
8 touches
6 conflicts
0x0ff4d33f…6dde
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x6d43ee99…bdda
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xb482658a15…f3e4f5
Audit this contract →
← previous block·next block →recent activity