← previous blocknext block →recent activity
Analyzing
Block #104,148,644
22 transactions · 21 stateful · 2026-09-12 09:50:45 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,148,644 · 22 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
1w02w13w24w311w115w216w317w418w519w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe410aa6…6697
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xc87e767e…4bba
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x3a3097d7…2ab7
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…00c9
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
15 conflicts on slot 0xfe410aa69f…e96697
Audit this contract →
← previous block·next block →recent activity