← previous blocknext block →recent activity

Analyzing

Block #106,552,071

29 transactions · 27 stateful · 2026-09-20 19:55:34 UTC

Parallelism

66/100

Blocked

59%

Avg conflicts / tx

1.79

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,552,071  ·  29 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

0xd62f3741…b903

0x34b655…2a6f

12 touches
15 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

10 touches
10 conflicts

0xb2560305…f27d

0x34b655…2a6f

10 touches
10 conflicts

0x1b25f260…c429

0x34b655…2a6f

10 touches
10 conflicts

0xad862891…5d02

0x34b655…2a6f

10 touches
10 conflicts

0xf90c6521…d8f0

0x34b655…2a6f

10 touches
10 conflicts

0xa8ff42d0…ab7e

0x34b655…2a6f

8 touches
6 conflicts

0x3639a9ac…3165

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

15 conflicts on slot 0xd62f374157…55b903

← previous block·next block →recent activity