← previous blocknext block →recent activity

Analyzing

Block #106,923,544

18 transactions · 18 stateful · 2026-09-22 03:06:14 UTC

Parallelism

56/100

Blocked

50%

Avg conflicts / tx

1.28

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,923,544  ·  18 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x46483cb1…e7ca

0x34b655…2a6f

12 touches
15 conflicts

0x85bfd0af…ce96

0x34b655…2a6f

8 touches
6 conflicts

0xb3d828cf…a9b8

0x34b655…2a6f

8 touches
6 conflicts

0x57bf1a1b…914e

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x8590b692…b267

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x4ec9ff52…e6f7

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

15 conflicts on slot 0x46483cb14f…c1e7ca

← previous block·next block →recent activity