← previous blocknext block →recent activity
Analyzing
Block #100,235,729
20 transactions · 17 stateful · 2026-08-29 16:47:12 UTC
Parallelism
65/100
Blocked
65%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,235,729 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w16w011w412w114w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c29ecd5…58b6
0x34b655…2a6f
12 touches
15 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
12 touches
15 conflicts
0xbd590df7…9891
0x34b655…2a6f
12 touches
15 conflicts
0xc3d31345…6bef
0xd32edf…ff58
9 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
8 touches
6 conflicts
0xcad937e9…7873
0x1b6862…e19c
6 touches
3 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 0x4c29ecd55a…1058b6
Audit this contract →
← previous block·next block →recent activity