← previous blocknext block →recent activity
Analyzing
Block #100,122,722
27 transactions · 26 stateful · 2026-08-29 07:18:13 UTC
Parallelism
63/100
Blocked
73%
Avg conflicts / tx
2.81
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,122,722 · 27 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
1w02w13w24w35w46w58w111w213w217w619w520w721w622w723w826w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x1eb1a4af…3b1d
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…00c9
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…641f
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x4979282b…2936
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity