← previous blocknext block →recent activity

Analyzing

Block #104,332,521

32 transactions · 29 stateful · 2026-09-13 01:23:46 UTC

Parallelism

72/100

Blocked

45%

Avg conflicts / tx

1.28

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #104,332,521  ·  32 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

14 touches
21 conflicts

0x705a9a1a…db08

0x34b655…2a6f

12 touches
15 conflicts

0x0a9de7e4…b2e4

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x879c7659…354c

0x34b655…2a6f

8 touches
6 conflicts

0x48b13e5e…3c2a

0x34b655…2a6f

4 touches
1 conflict

0x4e135144…4167

0x34b655…2a6f

4 touches
1 conflict

0x75e22f9e…38e1

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 0xc824469a90…af6425

← previous block·next block →recent activity