← previous blocknext block →recent activity
Analyzing
Block #100,139,735
24 transactions · 21 stateful · 2026-08-29 08:44:00 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,139,735 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w211w114w215w316w420w521w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6426
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe8d47602…c212
0x34b655…2a6f
10 touches
10 conflicts
0xa169711f…c7f3
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x79ce2c35…44f4
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
15 conflicts on slot 0xc824469a90…af6426
Audit this contract →
← previous block·next block →recent activity