← previous blocknext block →recent activity
Analyzing
Block #101,311,269
59 transactions · 49 stateful · 2026-09-02 11:02:34 UTC
Parallelism
71/100
Blocked
80%
Avg conflicts / tx
4.02
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #101,311,269 · 59 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w38w49w510w611w712w813w914w1016w444w158w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
34 touches
136 conflicts
0x00000000…003d
0x065c9d…c394
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x06e40499…165e
0x34ae4d…3fc5
16 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
16 touches
28 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
16 touches
28 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
16 touches
28 conflicts
0x8488f10f…9354
0x34ae4d…3fc5
12 touches
15 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: 0xf5b5f7f8…a36d70
136 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity