← previous blocknext block →recent activity
Analyzing
Block #101,661,889
37 transactions · 35 stateful · 2026-09-03 16:26:39 UTC
Parallelism
84/100
Blocked
57%
Avg conflicts / tx
1.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,661,889 · 37 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w010w115w316w217w218w322w323w424w529w132w234w435w536w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefb236ca…f49b
0x34b655…2a6f
12 touches
15 conflicts
0xe2be30ab…218d
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x84611dd3…b345
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 0xefb236ca8b…0ff49b
Audit this contract →
← previous block·next block →recent activity