← previous blocknext block →recent activity
Analyzing
Block #100,786,726
36 transactions · 34 stateful · 2026-08-31 15:03:08 UTC
Parallelism
72/100
Blocked
65%
Avg conflicts / tx
1.83
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,786,726 · 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
1w02w13w24w25w36w47w08w09w110w116w317w418w523w527w728w230w435w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76622fb2…4f08
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x81716ce9…095f
0x34b655…2a6f
8 touches
6 conflicts
0x3b37ec05…ccc7
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
21 conflicts on slot 0x76622fb2e3…024f08
Audit this contract →
← previous block·next block →recent activity