← previous blocknext block →recent activity
Analyzing
Block #101,062,623
88 transactions · 51 stateful · 2026-09-01 14:11:20 UTC
Parallelism
75/100
Blocked
82%
Avg conflicts / tx
2.15
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #101,062,623 · 88 txs across 22 waves · depth 22
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
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w07w18w210w311w412w565w170w571w176w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x737acb78…fce8
0x34b655…2a6f
20 touches
45 conflicts
0x41c56387…a8f6
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x3f2100d8…f9b5
0xa6afd3…d132
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: Perpl
55 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity