← previous blocknext block →recent activity
Analyzing
Block #103,212,169
15 transactions · 14 stateful · 2026-09-09 02:59:26 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #103,212,169 · 15 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
2w08w19w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
12 touches
15 conflicts
0xbd590df7…9891
0x34b655…2a6f
12 touches
15 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
10 touches
10 conflicts
0xbc5c1743…052c
0x34b655…2a6f
6 touches
3 conflicts
0xf70de18e…4ebd
0x34b655…2a6f
6 touches
3 conflicts
0x0d98a52f…666c
0x34b655…2a6f
5 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 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity