← previous blocknext block →recent activity
Analyzing
Block #106,282,002
40 transactions · 39 stateful · 2026-09-19 21:16:22 UTC
Parallelism
60/100
Blocked
62%
Avg conflicts / tx
3.55
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,282,002 · 40 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w18w210w316w317w418w519w622w723w726w827w930w1031w1132w1233w1334w1435w1537w1038w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdde34296…d676
0x34b655…2a6f
30 touches
105 conflicts
0xdc90bed5…58a9
0x34b655…2a6f
20 touches
45 conflicts
0x5b6af007…0f35
0x34b655…2a6f
16 touches
28 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
14 touches
21 conflicts
0xe098738f…9bbe
0x34b655…2a6f
14 touches
21 conflicts
0xc74a8532…6290
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7a43e31a…3cb5
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
105 conflicts on slot 0xdde3429633…a7d676
Audit this contract →
← previous block·next block →recent activity