← previous blocknext block →recent activity

Analyzing

Block #106,916,698

21 transactions · 20 stateful · 2026-09-22 02:31:47 UTC

Parallelism

43/100

Blocked

55%

Avg conflicts / tx

1.95

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #106,916,698  ·  21 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xd192f4ed…d7ec

0x34b655…2a6f

14 touches
21 conflicts

0xcc844ab5…4c6d

0x34b655…2a6f

14 touches
21 conflicts

0x4996be87…663a

0x34b655…2a6f

12 touches
15 conflicts

0x49890ced…6f23

0x34b655…2a6f

12 touches
15 conflicts

0xd9545ad3…62ea

0x34b655…2a6f

12 touches
15 conflicts

0xccebf5c5…8758

0x34b655…2a6f

12 touches
15 conflicts

0x3d2785ea…dd64

0x34b655…2a6f

4 touches
1 conflict

0x7f4a8466…f2cc

0x34ae4d…3fc5

2 touches
0 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

21 conflicts on slot 0xd192f4edae…03d7ec

← previous block·next block →recent activity