← previous blocknext block →recent activity
Analyzing
Block #103,987,700
21 transactions · 20 stateful · 2026-09-11 20:11:54 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,987,700 · 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
1w02w13w24w35w06w19w010w111w212w313w415w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dedaff6…161b
0x34b655…2a6f
14 touches
21 conflicts
0xef048f92…572b
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x077e96c0…df2c
0x34b655…2a6f
12 touches
15 conflicts
0x0942947e…563a
0x34b655…2a6f
12 touches
15 conflicts
0x45a7c210…d2d7
0x34b655…2a6f
12 touches
15 conflicts
0x86cea35b…bdff
0x34b655…2a6f
12 touches
15 conflicts
0x45b67460…28a7
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
21 conflicts on slot 0x6dedaff684…2d161b
Audit this contract →
← previous block·next block →recent activity