← previous blocknext block →recent activity
Analyzing
Block #101,967,709
59 transactions · 40 stateful · 2026-09-04 18:08:10 UTC
Parallelism
68/100
Blocked
75%
Avg conflicts / tx
2.22
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #101,967,709 · 59 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w414w315w516w617w718w519w646w950w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x51fc8795…126f
0x34b655…2a6f
16 touches
28 conflicts
0x48007f7e…1200
0xd32edf…ff58
15 touches
28 conflicts
0x045532dd…4b7d
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0x36918c55…8424
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity