← previous blocknext block →recent activity

Analyzing

Block #104,916,524

22 transactions · 21 stateful · 2026-09-15 02:41:23 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #104,916,524  ·  22 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

0xfd7f5b55…4994

0x34b655…2a6f

12 touches
15 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x4d4389b2…6e07

0x34b655…2a6f

8 touches
6 conflicts

0xedbdafc3…1492

0x34b655…2a6f

8 touches
6 conflicts

0xff7cb355…3404

0x34b655…2a6f

8 touches
6 conflicts

0x90bbbced…dac6

0x34b655…2a6f

6 touches
3 conflicts

0x206f4379…e08a

0x34b655…2a6f

6 touches
3 conflicts

0xf79df061…e005

0xe52b14…7230

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

15 conflicts on slot 0xfd7f5b557f…f74994

← previous block·next block →recent activity