← previous blocknext block →recent activity

Analyzing

Block #104,192,635

20 transactions · 19 stateful · 2026-09-12 13:33:57 UTC

Parallelism

45/100

Blocked

63%

Avg conflicts / tx

2.3

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #104,192,635  ·  20 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

0xd89c163d…101e

0x34b655…2a6f

16 touches
28 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

14 touches
21 conflicts

0xf72228f6…970c

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x45de70d9…e1dc

0x34b655…2a6f

8 touches
6 conflicts

0xd0fd6c76…ddaf

0x34b655…2a6f

8 touches
6 conflicts

0x8299fe6c…5752

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 0xd89c163d01…a1101e

← previous block·next block →recent activity