← previous blocknext block →recent activity
Analyzing
Block #100,057,215
20 transactions · 18 stateful · 2026-08-29 01:48:23 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,057,215 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w210w412w314w416w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9912c5c1…f552
0x34b655…2a6f
12 touches
15 conflicts
0x5e478d45…5679
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x0a6cb118…4ca7
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
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
15 conflicts on slot 0x9912c5c1b7…f9f552
Audit this contract →
← previous block·next block →recent activity