← previous blocknext block →recent activity

Analyzing

Block #104,877,272

22 transactions · 21 stateful · 2026-09-14 23:23:53 UTC

Parallelism

55/100

Blocked

48%

Avg conflicts / tx

1.09

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #104,877,272  ·  22 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

0xac389ba9…8b45

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x03500bec…db28

0x34b655…2a6f

6 touches
3 conflicts

0xb550abea…2729

0x34b655…2a6f

6 touches
3 conflicts

0x3663f867…8995

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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

15 conflicts on slot 0xac389ba9d1…e18b45

← previous block·next block →recent activity