← previous blocknext block →recent activity

Analyzing

Block #106,420,556

21 transactions · 20 stateful · 2026-09-20 08:53:37 UTC

Parallelism

48/100

Blocked

65%

Avg conflicts / tx

1.76

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #106,420,556  ·  21 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x84e381f6…3da3

0x34b655…2a6f

12 touches
15 conflicts

0xbe9d1d23…3de2

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x5e1c23e9…4f81

0x34b655…2a6f

8 touches
6 conflicts

0xba9f9225…2ead

0x34b655…2a6f

8 touches
6 conflicts

0xe4cd2876…82ab

0x34b655…2a6f

8 touches
6 conflicts

0x810a3aa2…0227

0x34b655…2a6f

6 touches
3 conflicts

0x1b25f260…c429

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

15 conflicts on slot 0x84e381f6af…4b3da3

← previous block·next block →recent activity