← previous blocknext block →recent activity
Analyzing
Block #101,251,817
73 transactions · 59 stateful · 2026-09-02 06:03:25 UTC
Parallelism
73/100
Blocked
80%
Avg conflicts / tx
4.22
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #101,251,817 · 73 txs across 20 waves · depth 20
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
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w38w49w511w612w718w836w137w145w946w1057w459w660w763w1064w1166w1368w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
36 touches
153 conflicts
0x54371e2f…80c6
0xd32edf…ff58
21 touches
55 conflicts
0x00000000…0002
0xf5b5f7…6d70
18 touches
36 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0x737acb78…fce8
0x34b655…2a6f
16 touches
28 conflicts
0xd25997d0…a686
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001b
0x1b6862…e19c
14 touches
21 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
153 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity