← previous blocknext block →recent activity

Analyzing

Block #106,367,185

26 transactions · 23 stateful · 2026-09-20 04:25:02 UTC

Parallelism

62/100

Blocked

57%

Avg conflicts / tx

1.58

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,367,185  ·  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

0x065a3bb1…e176

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xaaa09a9b…4fed

0x34b655…2a6f

8 touches
6 conflicts

0x74e46435…fdcd

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x0262e1c6…52e1

0x34b655…2a6f

8 touches
6 conflicts

0x89eaf36a…4e48

0x34b655…2a6f

8 touches
6 conflicts

0x8d664414…3344

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 0x065a3bb1e1…4ce176

← previous block·next block →recent activity