← previous blocknext block →recent activity
Analyzing
Block #101,659,621
34 transactions · 30 stateful · 2026-09-03 16:15:15 UTC
Parallelism
44/100
Blocked
80%
Avg conflicts / tx
3.32
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #101,659,621 · 34 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
1w02w13w24w35w47w28w39w413w516w617w520w621w723w825w1027w1229w1430w1531w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x51fc8795…126f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x7dd96c96…7335
0x34b655…2a6f
10 touches
10 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
10 touches
10 conflicts
0x65f011a5…bc6e
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity