← previous blocknext block →recent activity

Analyzing

Block #107,847,732

25 transactions · 24 stateful · 2026-09-25 08:40:28 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.72

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #107,847,732  ·  25 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

0xecff7c35…1b43

0x34b655…2a6f

18 touches
36 conflicts

0x2a25e46d…9fad

0x34b655…2a6f

12 touches
15 conflicts

0x0db691ab…3ee3

0x34b655…2a6f

10 touches
10 conflicts

0xb1cec296…36e4

0x34b655…2a6f

10 touches
10 conflicts

0x49890ced…6f23

0x34b655…2a6f

10 touches
10 conflicts

0x3d93ad2c…e747

0x34b655…2a6f

10 touches
10 conflicts

0xe3fa5262…0e0c

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 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 0xecff7c3510…111b43

← previous block·next block →recent activity