← previous blocknext block →recent activity
Analyzing
Block #101,800,119
16 transactions · 15 stateful · 2026-09-04 04:01:55 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,800,119 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w010w011w112w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8f860c0…35c9
0x34b655…2a6f
10 touches
10 conflicts
0x3d13406e…eff1
0x34b655…2a6f
10 touches
10 conflicts
0x4f3cc09a…2804
0x34b655…2a6f
10 touches
10 conflicts
0x53e08444…d671
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0xa16bf106…d9ed
0x34b655…2a6f
10 touches
10 conflicts
0xb3e293fe…be2e
0x34b655…2a6f
10 touches
10 conflicts
0xb40e601f…bf98
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
10 conflicts on slot 0xe8f860c039…3435c9
Audit this contract →
← previous block·next block →recent activity