← previous blocknext block →recent activity
Analyzing
Block #100,056,288
66 transactions · 52 stateful · 2026-08-29 01:43:43 UTC
Parallelism
67/100
Blocked
85%
Avg conflicts / tx
3.3
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #100,056,288 · 66 txs across 22 waves · depth 22
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w111w013w114w115w218w320w236w237w338w439w540w641w743w444w146w549w253w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0x00000000…0002
0xf5b5f7…6d70
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x42daad7f…630b
0xa6afd3…d132
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity