← previous blocknext block →recent activity

Analyzing

Block #106,469,654

19 transactions · 18 stateful · 2026-09-20 13:00:47 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,469,654  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe0d9ed00…4e8d

0x34b655…2a6f

6 touches
3 conflicts

0x27b85bff…02f7

0x34b655…2a6f

4 touches
1 conflict

0x2aab0897…78f7

0x34b655…2a6f

4 touches
1 conflict

0x4118bd12…924a

0x34b655…2a6f

4 touches
1 conflict

0x49b9fdd5…9c16

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x668d864b…c1e0

0x34b655…2a6f

4 touches
1 conflict

0x727c4cf7…94b4

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

3 conflicts on slot 0xe0d9ed0076…884e8d

← previous block·next block →recent activity