← previous blocknext block →recent activity

Analyzing

Block #104,869,439

19 transactions · 18 stateful · 2026-09-14 22:44:28 UTC

Parallelism

58/100

Blocked

50%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #104,869,439  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd9722304…6ed0

0x34b655…2a6f

14 touches
21 conflicts

0x0c5747f0…710b

0x34b655…2a6f

8 touches
6 conflicts

0x711ceb8d…5202

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x736fafee…8bfc

0x34b655…2a6f

6 touches
3 conflicts

0xa2612d83…e342

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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

21 conflicts on slot 0xd97223041d…366ed0

← previous block·next block →recent activity