← previous blocknext block →recent activity

Analyzing

Block #104,704,122

17 transactions · 17 stateful · 2026-09-14 08:50:04 UTC

Parallelism

59/100

Blocked

53%

Avg conflicts / tx

1.18

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #104,704,122  ·  17 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0xb75367ff…a2b7

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x25d5e04e…3ef4

0x754704…b603

4 touches
1 conflict

0x64b004ab…60af

0x754704…b603

4 touches
1 conflict

0xba68e65e…c29a

0x754704…b603

4 touches
1 conflict

0xb14cff21…59e9

0x99c7a7…8bf0

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity