← previous blocknext block →recent activity
Analyzing
Block #101,023,051
24 transactions · 22 stateful · 2026-09-01 10:52:14 UTC
Parallelism
71/100
Blocked
64%
Avg conflicts / tx
1.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,023,051 · 24 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
1w02w13w24w35w19w210w311w413w514w519w220w323w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25ebe5e6…1791
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x8db32935…81a7
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x2bbc0cfb…c2c2
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
15 conflicts on slot 0x25ebe5e685…af1791
Audit this contract →
← previous block·next block →recent activity