← previous blocknext block →recent activity

Analyzing

Block #104,877,300

25 transactions · 24 stateful · 2026-09-14 23:24:01 UTC

Parallelism

76/100

Blocked

46%

Avg conflicts / tx

1.16

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #104,877,300  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xa2ff4baa…16f4

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xac389ba9…8b45

0x34b655…2a6f

8 touches
6 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x299e547d…af09

0x34b655…2a6f

6 touches
3 conflicts

0x81716ce9…095f

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xdcd58096…bb7a

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

10 conflicts on slot 0xa2ff4baa42…aa16f4

← previous block·next block →recent activity