← previous blocknext block →recent activity
Analyzing
Block #100,605,386
39 transactions · 35 stateful · 2026-08-30 23:50:47 UTC
Parallelism
62/100
Blocked
69%
Avg conflicts / tx
3.28
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #100,605,386 · 39 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w010w011w112w114w316w317w418w420w121w524w125w226w327w428w529w630w731w832w933w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
30 touches
105 conflicts
0x92385428…6941
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0x886db264…846e
0x34b655…2a6f
18 touches
36 conflicts
0xe7aef4d2…32cb
0x34b655…2a6f
10 touches
10 conflicts
0xc95f91db…a901
0x34b655…2a6f
10 touches
10 conflicts
0xd7322298…e423
0xd32edf…ff58
9 touches
10 conflicts
0xded7831c…3c4a
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
105 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity