← previous blocknext block →recent activity
Analyzing
Block #101,062,022
33 transactions · 29 stateful · 2026-09-01 14:08:19 UTC
Parallelism
67/100
Blocked
69%
Avg conflicts / tx
1.48
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #101,062,022 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w07w39w011w112w215w316w417w418w520w422w124w625w126w227w329w731w932w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf65c9ad4…88f7
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x6b1259e6…4e0d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x70e677f5…e3bd
0x34b655…2a6f
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
10 conflicts on slot 0xf65c9ad483…3388f7
Audit this contract →
← previous block·next block →recent activity