← previous blocknext block →recent activity

Analyzing

Block #104,704,083

24 transactions · 22 stateful · 2026-09-14 08:49:52 UTC

Parallelism

58/100

Blocked

45%

Avg conflicts / tx

0.75

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #104,704,083  ·  24 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

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x61571888…b392

0x34b655…2a6f

6 touches
3 conflicts

0xf98c943e…7c44

0x34b655…2a6f

6 touches
3 conflicts

0x6726896b…7935

0x754704…b603

4 touches
1 conflict

0x6c54aa60…40ec

0x754704…b603

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity