← previous blocknext block →recent activity
Analyzing
Block #100,790,403
81 transactions · 58 stateful · 2026-08-31 15:21:39 UTC
Parallelism
69/100
Blocked
78%
Avg conflicts / tx
2.59
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #100,790,403 · 81 txs across 25 waves · depth 25
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
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
wave w24
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w415w516w617w748w952w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
30 touches
105 conflicts
0xfbd60747…f478
0xd32edf…ff58
17 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
16 touches
28 conflicts
0x886db264…846e
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x482471ad…122f
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