← previous blocknext block →recent activity
Analyzing
Block #101,302,480
25 transactions · 20 stateful · 2026-09-02 10:18:20 UTC
Parallelism
72/100
Blocked
45%
Avg conflicts / tx
0.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,302,480 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w27w18w39w210w311w422w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec1d6663…6042
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x71b78a6f…3ddc
0x34b655…2a6f
6 touches
3 conflicts
0x90d24713…b88c
0x1b6862…e19c
6 touches
3 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 0xec1d6663f8…f86042
Audit this contract →
← previous block·next block →recent activity