← previous blocknext block →recent activity
Analyzing
Block #100,140,724
40 transactions · 35 stateful · 2026-08-29 08:48:59 UTC
Parallelism
75/100
Blocked
71%
Avg conflicts / tx
2.25
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,140,724 · 40 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
1w02w13w24w36w47w510w015w416w617w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x1e168c8b…6945
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x98ea7c1f…bd8f
0xd32edf…ff58
9 touches
10 conflicts
0xba5743c7…21c4
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity