← previous blocknext block →recent activity

Analyzing

Block #106,109,610

21 transactions · 20 stateful · 2026-09-19 06:48:40 UTC

Parallelism

48/100

Blocked

70%

Avg conflicts / tx

2.71

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #106,109,610  ·  21 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x4fbd0a79…626a

0x34b655…2a6f

14 touches
21 conflicts

0xbf8a0ace…7ac7

0x34b655…2a6f

12 touches
15 conflicts

0x735a86cd…b64d

0x34b655…2a6f

10 touches
10 conflicts

0x2a2896a0…2a0a

0x34b655…2a6f

10 touches
10 conflicts

0xf6d87ec7…42eb

0x34b655…2a6f

10 touches
10 conflicts

0x9256b810…52cc

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x49890ced…6f23

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

21 conflicts on slot 0x4fbd0a7965…4c626a

← previous block·next block →recent activity