← previous blocknext block →recent activity

Analyzing

Block #106,917,430

25 transactions · 23 stateful · 2026-09-22 02:35:28 UTC

Parallelism

64/100

Blocked

48%

Avg conflicts / tx

1.28

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #106,917,430  ·  25 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

0x85bfd0af…ce96

0x34b655…2a6f

14 touches
21 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

12 touches
15 conflicts

0x61da5094…a3c9

0x34b655…2a6f

12 touches
15 conflicts

0xfcc8f826…7c5f

0x34b655…2a6f

10 touches
10 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0xf7ed92bb…24eb

0x34b655…2a6f

8 touches
6 conflicts

0x7d228d06…6dd6

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

21 conflicts on slot 0x85bfd0afba…f5ce96

← previous block·next block →recent activity