← previous blocknext block →recent activity

Analyzing

Block #106,253,102

22 transactions · 21 stateful · 2026-09-19 18:50:56 UTC

Parallelism

68/100

Blocked

43%

Avg conflicts / tx

1.09

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,253,102  ·  22 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xfccf4b5b…66ca

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xee56e2b2…7d47

0x34b655…2a6f

12 touches
15 conflicts

0x5906754f…b584

0x34b655…2a6f

8 touches
6 conflicts

0x524f0872…0d12

0x34b655…2a6f

6 touches
3 conflicts

0x6204bd9b…82dc

0x34b655…2a6f

6 touches
3 conflicts

0x94e7f277…471b

0x34b655…2a6f

6 touches
3 conflicts

0x49b9fdd5…9c16

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

15 conflicts on slot 0xfccf4b5b29…a966ca

← previous block·next block →recent activity