← previous blocknext block →recent activity

Analyzing

Block #105,435,376

21 transactions · 18 stateful · 2026-09-16 22:12:50 UTC

Parallelism

86/100

Blocked

39%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #105,435,376  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbb4d285d…4988

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x7c51d9aa…af39

0x34b655…2a6f

6 touches
3 conflicts

0xf6deafb5…5c25

0x34b655…2a6f

6 touches
3 conflicts

0xb577e91d…1a81

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xb5dac821…b68b

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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 0xbb4d285d37…824988

← previous block·next block →recent activity