← previous blocknext block →recent activity

Analyzing

Block #106,916,844

25 transactions · 21 stateful · 2026-09-22 02:32:31 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,916,844  ·  25 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

0xba1edffb…323e

0x34b655…2a6f

8 touches
6 conflicts

0x69411fb3…e36d

0x34b655…2a6f

8 touches
6 conflicts

0x3a0218bf…e2a3

0x34b655…2a6f

6 touches
3 conflicts

0xf7ae2120…d1d2

0x34b655…2a6f

6 touches
3 conflicts

0xccebf5c5…8758

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x8475a8f9…c235

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

6 conflicts on slot 0xba1edffb42…64323e

← previous block·next block →recent activity