← previous blocknext block →recent activity

Analyzing

Block #104,148,977

24 transactions · 22 stateful · 2026-09-12 09:52:27 UTC

Parallelism

58/100

Blocked

55%

Avg conflicts / tx

2.33

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #104,148,977  ·  24 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

0x705a9a1a…db08

0x34b655…2a6f

20 touches
45 conflicts

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0xf1352320…c9c3

0x34b655…2a6f

12 touches
15 conflicts

0x38bcfe5f…6c71

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6426

0x34b655…2a6f

8 touches
6 conflicts

0x6063a926…0be4

0x34b655…2a6f

8 touches
6 conflicts

0xb839a1e8…22b3

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

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

45 conflicts on slot 0x705a9a1af8…69db08

← previous block·next block →recent activity