← previous blocknext block →recent activity
Analyzing
Block #104,204,977
19 transactions · 19 stateful · 2026-09-12 14:36:47 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,204,977 · 19 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
1w02w13w24w05w16w39w212w313w414w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x7bef9f87…a533
0x34b655…2a6f
10 touches
10 conflicts
0x6dedaff6…161b
0x34b655…2a6f
10 touches
10 conflicts
0x1e2541ff…0188
0x34b655…2a6f
8 touches
6 conflicts
0x27754bd4…96ae
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x0deb5804…40c6
0x34b655…2a6f
6 touches
3 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