← previous blocknext block →recent activity

Analyzing

Block #106,362,328

19 transactions · 19 stateful · 2026-09-20 04:00:35 UTC

Parallelism

47/100

Blocked

58%

Avg conflicts / tx

2.79

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,362,328  ·  19 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

18 touches
36 conflicts

0x9ca9fcbb…3982

0x34b655…2a6f

18 touches
36 conflicts

0xba33378a…f1df

0x34b655…2a6f

14 touches
21 conflicts

0x5edd6cd5…e729

0x34b655…2a6f

12 touches
15 conflicts

0x53ca1284…cb2c

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x810a3aa2…0227

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

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

36 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity