← previous blocknext block →recent activity

Analyzing

Block #106,389,021

24 transactions · 23 stateful · 2026-09-20 06:14:55 UTC

Parallelism

58/100

Blocked

52%

Avg conflicts / tx

1.63

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,389,021  ·  24 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x1e665745…8517

0x34b655…2a6f

14 touches
21 conflicts

0xba33378a…f1df

0x34b655…2a6f

12 touches
15 conflicts

0x2a21beda…27eb

0x34b655…2a6f

8 touches
6 conflicts

0x54f7f60f…43cc

0x34b655…2a6f

8 touches
6 conflicts

0x310a7246…2dcb

0x34b655…2a6f

8 touches
6 conflicts

0x93afca4c…b47a

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x1b25f260…c429

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

21 conflicts on slot 0x1e66574536…6d8517

← previous block·next block →recent activity