← previous blocknext block →recent activity

Analyzing

Block #106,955,674

21 transactions · 16 stateful · 2026-09-22 05:47:58 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,955,674  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf3b2c2e6…31e9

0x34b655…2a6f

6 touches
3 conflicts

0xc4c059d8…185d

0x34b655…2a6f

6 touches
3 conflicts

0x95523e2a…4c01

0x065c9d…c394

6 touches
3 conflicts

0xc2c49f37…e17a

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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

3 conflicts on slot 0x49890ced8d…316f23

← previous block·next block →recent activity