← previous blocknext block →recent activity

Analyzing

Block #104,205,238

28 transactions · 25 stateful · 2026-09-12 14:38:07 UTC

Parallelism

64/100

Blocked

44%

Avg conflicts / tx

1.75

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #104,205,238  ·  28 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

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0x482471ad…122f

0x34b655…2a6f

16 touches
28 conflicts

0xf3a5636c…14e8

0x34b655…2a6f

14 touches
21 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6426

0x34b655…2a6f

6 touches
3 conflicts

0x6c0bfcd8…55a7

0x34b655…2a6f

5 touches
3 conflicts

0x939cdd56…00c8

0x34b655…2a6f

4 touches
1 conflict

0x9d9f3717…44e7

0x34b655…2a6f

4 touches
1 conflict

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 0xc824469a90…af6425

← previous block·next block →recent activity