← previous blocknext block →recent activity

Analyzing

Block #106,393,335

26 transactions · 24 stateful · 2026-09-20 06:36:38 UTC

Parallelism

62/100

Blocked

54%

Avg conflicts / tx

1.15

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,393,335  ·  26 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

0x990cc6f8…0e7b

0x34b655…2a6f

12 touches
15 conflicts

0x70986451…c6bd

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x8d175439…fb79

0x34b655…2a6f

6 touches
3 conflicts

0x0262e1c6…52e1

0x34b655…2a6f

6 touches
3 conflicts

0x0dd3d3cd…7281

0x34b655…2a6f

6 touches
3 conflicts

0x49b9fdd5…9c16

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

15 conflicts on slot 0x990cc6f828…0f0e7b

← previous block·next block →recent activity