← previous blocknext block →recent activity

Analyzing

Block #102,444,375

23 transactions · 21 stateful · 2026-09-06 10:23:42 UTC

Parallelism

61/100

Blocked

43%

Avg conflicts / tx

1.91

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #102,444,375  ·  23 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

0xd98b3c10…67b8

0x34b655…2a6f

18 touches
36 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

8 touches
6 conflicts

0x46c14e01…ff09

0x34b655…2a6f

8 touches
6 conflicts

0x57be321f…fecc

0x34b655…2a6f

6 touches
3 conflicts

0x3cf31547…051b

0x34b655…2a6f

6 touches
3 conflicts

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity