← previous blocknext block →recent activity

Analyzing

Block #106,184,571

24 transactions · 23 stateful · 2026-09-19 13:05:56 UTC

Parallelism

58/100

Blocked

52%

Avg conflicts / tx

2.04

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,184,571  ·  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

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0xd022c24c…ee45

0x34b655…2a6f

16 touches
28 conflicts

0x0fc536fb…1aa1

0x34b655…2a6f

14 touches
21 conflicts

0x1d351a9b…f2dd

0x34b655…2a6f

8 touches
6 conflicts

0xbeedaa05…9eda

0x34b655…2a6f

6 touches
3 conflicts

0xa6464996…3af9

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

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

28 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity