← previous blocknext block →recent activity

Analyzing

Block #106,425,623

18 transactions · 18 stateful · 2026-09-20 09:19:07 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.61

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,425,623  ·  18 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

0xd0c4deed…34e1

0x34b655…2a6f

12 touches
15 conflicts

0x2c2761c0…476e

0x34b655…2a6f

10 touches
10 conflicts

0x7cd9fd28…a158

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x38bcfe5f…6c71

0x34b655…2a6f

6 touches
3 conflicts

0x80398c66…f3cc

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x49b9fdd5…9c16

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

15 conflicts on slot 0xd0c4deede9…7434e1

← previous block·next block →recent activity