← previous blocknext block →recent activity

Analyzing

Block #106,046,691

55 transactions · 53 stateful · 2026-09-19 01:32:02 UTC

Parallelism

91/100

Blocked

15%

Avg conflicts / tx

0.29

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,046,691  ·  55 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x08f9abf1…10bf

0x34b655…2a6f

8 touches
6 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x6f58168d…ea24

0x34b655…2a6f

6 touches
3 conflicts

0x7a2fc410…c088

0x34b655…2a6f

5 touches
3 conflicts

0x085df2c1…305a

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

10 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity