← previous blocknext block →recent activity
Analyzing
Block #106,215,618
18 transactions · 17 stateful · 2026-09-19 15:42:14 UTC
Parallelism
44/100
Blocked
53%
Avg conflicts / tx
2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,215,618 · 18 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w28w39w410w511w613w814w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x638cd0f2…cb93
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe2ce5557…ab10
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0x2d84ae4b…161b
0x34b655…2a6f
6 touches
3 conflicts
0x7a1c8aca…40b1
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
28 conflicts on slot 0x638cd0f243…88cb93
Audit this contract →
← previous block·next block →recent activity