← previous blocknext block →recent activity
Analyzing
Block #104,160,173
21 transactions · 20 stateful · 2026-09-12 10:49:23 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,160,173 · 21 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
1w02w15w212w313w414w515w616w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x1a2055c7…9054
0x34b655…2a6f
10 touches
10 conflicts
0xb7b9b7e8…4715
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0xd7908b5f…56b9
0x34b655…2a6f
10 touches
10 conflicts
0x640c4fb2…044a
0x34b655…2a6f
9 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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity