← previous blocknext block →recent activity

Analyzing

Block #106,538,809

24 transactions · 22 stateful · 2026-09-20 18:48:50 UTC

Parallelism

71/100

Blocked

45%

Avg conflicts / tx

1.13

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,538,809  ·  24 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

0xa2471b4c…0c19

0x34b655…2a6f

14 touches
21 conflicts

0x39561c15…c70f

0x34b655…2a6f

12 touches
15 conflicts

0xa3ed5a09…c6d3

0x34b655…2a6f

8 touches
6 conflicts

0x6b267bdf…b173

0x34b655…2a6f

8 touches
6 conflicts

0x4be9812b…48a9

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x1b25f260…c429

0x34b655…2a6f

4 touches
1 conflict

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 0xa2471b4c7f…2b0c19

← previous block·next block →recent activity