← previous blocknext block →recent activity

Analyzing

Block #106,099,911

21 transactions · 20 stateful · 2026-09-19 05:59:52 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,099,911  ·  21 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

0xe5eb3c33…0e3a

0x34b655…2a6f

8 touches
6 conflicts

0x85eb1316…bb9e

0x34b655…2a6f

8 touches
6 conflicts

0xdc90bed5…58a9

0x34b655…2a6f

6 touches
3 conflicts

0xe496f67d…65cf

0x34b655…2a6f

6 touches
3 conflicts

0xfd426e0d…be2b

0x34b655…2a6f

6 touches
3 conflicts

0xe8f6e3a8…d663

0xd32edf…ff58

5 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x214f87c0…9db8

0x34b655…2a6f

4 touches
1 conflict

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

6 conflicts on slot 0xe5eb3c3335…0c0e3a

← previous block·next block →recent activity