← previous blocknext block →recent activity
Analyzing
Block #100,605,717
35 transactions · 33 stateful · 2026-08-30 23:52:27 UTC
Parallelism
63/100
Blocked
61%
Avg conflicts / tx
2.66
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #100,605,717 · 35 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w29w010w114w315w016w117w018w020w321w423w124w225w326w427w528w629w730w831w932w1033w1134w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x6c6f37ba…c20c
0x1b6862…e19c
6 touches
3 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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity