← previous blocknext block →recent activity
Analyzing
Block #100,614,012
50 transactions · 45 stateful · 2026-08-31 00:34:11 UTC
Parallelism
68/100
Blocked
64%
Avg conflicts / tx
2.22
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #100,614,012 · 50 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w08w19w210w011w012w113w014w126w227w329w430w334w335w436w539w540w641w747w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0002
0xf5b5f7…6d70
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x1d10f24a…2fb8
0xa6afd3…d132
10 touches
10 conflicts
0xc45e4fb5…7cc3
0xa6afd3…d132
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity