← previous blocknext block →recent activity
Analyzing
Block #100,103,389
14 transactions · 13 stateful · 2026-08-29 05:40:50 UTC
Parallelism
36/100
Blocked
62%
Avg conflicts / tx
2.21
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,103,389 · 14 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w58w69w710w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x684b830d…d19e
0x34b655…2a6f
10 touches
10 conflicts
0x24bb46f7…3853
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x2b076ca1…6204
0x34b655…2a6f
6 touches
3 conflicts
0xa019dd86…b976
0x34b655…2a6f
6 touches
3 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity