← previous blocknext block →recent activity

Analyzing

Block #106,388,220

23 transactions · 22 stateful · 2026-09-20 06:10:54 UTC

Parallelism

70/100

Blocked

41%

Avg conflicts / tx

1.26

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,388,220  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x3f5831e5…02b2

0x34b655…2a6f

10 touches
10 conflicts

0x64275949…d698

0x34b655…2a6f

10 touches
10 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

10 touches
10 conflicts

0xd563f3a1…94b1

0x34b655…2a6f

9 touches
10 conflicts

0x20994928…2ff8

0x34b655…2a6f

8 touches
6 conflicts

0x2533fe3f…344d

0x34b655…2a6f

8 touches
6 conflicts

0x81655c1d…c4fd

0x34b655…2a6f

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 0x3f5831e5e5…ee02b2

← previous block·next block →recent activity