← previous blocknext block →recent activity

Analyzing

Block #106,235,175

37 transactions · 34 stateful · 2026-09-19 17:20:43 UTC

Parallelism

73/100

Blocked

41%

Avg conflicts / tx

1.49

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,235,175  ·  37 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

0xe47b6989…c993

0x34b655…2a6f

16 touches
28 conflicts

0xf00e711b…c539

0x34b655…2a6f

14 touches
21 conflicts

0xd66696e0…0842

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xff3d91c4…1a37

0x34b655…2a6f

8 touches
6 conflicts

0x310a7246…2dcb

0x34b655…2a6f

8 touches
6 conflicts

0x0e4fa697…08ca

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 0xe47b69896f…23c993

← previous block·next block →recent activity