← previous blocknext block →recent activity

Analyzing

Block #106,923,297

21 transactions · 21 stateful · 2026-09-22 03:05:00 UTC

Parallelism

57/100

Blocked

52%

Avg conflicts / tx

1.38

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #106,923,297  ·  21 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x70986451…c6bd

0x34b655…2a6f

12 touches
15 conflicts

0xba1edffb…323e

0x34b655…2a6f

10 touches
10 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

8 touches
6 conflicts

0x9670dc06…c488

0x34b655…2a6f

8 touches
6 conflicts

0x3780a34a…b50a

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x206f4379…e08a

0x34b655…2a6f

6 touches
3 conflicts

0x53690737…855a

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 0x7098645134…3ac6bd

← previous block·next block →recent activity