← previous blocknext block →recent activity

Analyzing

Block #106,362,287

20 transactions · 19 stateful · 2026-09-20 04:00:23 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

1.2

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,362,287  ·  20 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

0xc8cb0701…3926

0x34b655…2a6f

10 touches
10 conflicts

0xe0c6057d…49e9

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

8 touches
6 conflicts

0x511f46a7…edaa

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x1b25f260…c429

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

10 conflicts on slot 0xc8cb070152…393926

← previous block·next block →recent activity