← previous blocknext block →recent activity

Analyzing

Block #106,189,466

20 transactions · 19 stateful · 2026-09-19 13:30:34 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #106,189,466  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xb654bd89…a83b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2d071de0…c86e

0x34b655…2a6f

4 touches
1 conflict

0x581b829b…9578

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xf5b5f7…6d70

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0xe7013779…71d5

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0005

0x354d92…66fb

2 touches
0 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

3 conflicts on slot 0xb654bd89ad…dba83b

← previous block·next block →recent activity