← previous blocknext block →recent activity
Analyzing
Block #100,567,618
36 transactions · 29 stateful · 2026-08-30 20:40:47 UTC
Parallelism
72/100
Blocked
59%
Avg conflicts / tx
1.36
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,567,618 · 36 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
1w02w13w24w36w49w510w614w520w621w422w623w734w835w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xf4e34b80…8b0a
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x3a3097d7…2ab8
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x41f621e0…9e98
0x34b655…2a6f
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity