← previous blocknext block →recent activity

Analyzing

Block #104,167,000

24 transactions · 21 stateful · 2026-09-12 11:24:01 UTC

Parallelism

54/100

Blocked

71%

Avg conflicts / tx

2.29

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #104,167,000  ·  24 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

14 touches
21 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

12 touches
15 conflicts

0x5d6da397…6c5c

0x34b655…2a6f

12 touches
15 conflicts

0xa7c7b00e…bc2e

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x898d9b8a…d1ef

0x34b655…2a6f

8 touches
6 conflicts

0xa2869417…b1cb

0x34b655…2a6f

8 touches
6 conflicts

0x39126904…24d8

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity