← previous blocknext block →recent activity
Analyzing
Block #101,310,070
31 transactions · 30 stateful · 2026-09-02 10:56:32 UTC
Parallelism
58/100
Blocked
57%
Avg conflicts / tx
1.55
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #101,310,070 · 31 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w08w517w619w722w123w724w826w827w930w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b595a5d…894c
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd87390c9…3dca
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xd0ec60a1…d245
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x482471ad…122f
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
10 conflicts on slot 0x6b595a5d7d…1f894c
Audit this contract →
← previous block·next block →recent activity