← previous blocknext block →recent activity

Analyzing

Block #104,161,153

26 transactions · 25 stateful · 2026-09-12 10:54:19 UTC

Parallelism

65/100

Blocked

56%

Avg conflicts / tx

2

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #104,161,153  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xbcbf5d09…8bac

0x34b655…2a6f

18 touches
36 conflicts

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x2844358e…898f

0x34b655…2a6f

10 touches
10 conflicts

0x5d6da397…6c5c

0x34b655…2a6f

6 touches
3 conflicts

0xd5c98027…9fd9

0x34b655…2a6f

6 touches
3 conflicts

0x705a9a1a…db08

0x34b655…2a6f

6 touches
3 conflicts

0xe7b9eede…2538

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity