← previous blocknext block →recent activity
Analyzing
Block #100,895,410
32 transactions · 29 stateful · 2026-09-01 00:10:06 UTC
Parallelism
69/100
Blocked
72%
Avg conflicts / tx
1.72
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,895,410 · 32 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
1w02w13w24w35w49w311w512w618w219w320w721w323w425w626w727w829w731w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c6a9da2…c628
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xded216ce…191a
0xa6afd3…d132
10 touches
10 conflicts
0x8ef7b323…4ced
0xd32edf…ff58
9 touches
10 conflicts
0x3af0dd8e…0025
0x1b6862…e19c
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 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 0x9c6a9da253…d0c628
Audit this contract →
← previous block·next block →recent activity