← previous blocknext block →recent activity

Analyzing

Block #106,413,282

21 transactions · 20 stateful · 2026-09-20 08:17:01 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,413,282  ·  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

0xee4fe1f7…3ead

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xc34a9068…6b7f

0x34b655…2a6f

8 touches
6 conflicts

0x97d83630…cfc4

0x34b655…2a6f

8 touches
6 conflicts

0x97d5efed…1aa4

0x34b655…2a6f

6 touches
3 conflicts

0xc9d084aa…efb7

0x34b655…2a6f

6 touches
3 conflicts

0xf35cd327…9743

0x34b655…2a6f

6 touches
3 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 0xee4fe1f73e…483ead

← previous block·next block →recent activity