← previous blocknext block →recent activity

Analyzing

Block #106,381,537

18 transactions · 18 stateful · 2026-09-20 05:37:16 UTC

Parallelism

44/100

Blocked

61%

Avg conflicts / tx

2.78

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,381,537  ·  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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x366e63bf…8a96

0x34b655…2a6f

16 touches
28 conflicts

0xcd9ba26b…108d

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xe8058ec4…ebac

0x34b655…2a6f

8 touches
6 conflicts

0x4402c2ee…a884

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x3e6302c8…64f5

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

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

28 conflicts on slot 0x366e63bfaf…728a96

← previous block·next block →recent activity