← previous blocknext block →recent activity

Analyzing

Block #106,014,732

24 transactions · 21 stateful · 2026-09-18 22:51:12 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #106,014,732  ·  24 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

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x6ede85f4…0b8a

0x928dc8…8207

4 touches
1 conflict

0x6ede85f4…0b8b

0x928dc8…8207

4 touches
1 conflict

0x8dca7cdd…b416

0x928dc8…8207

4 touches
1 conflict

0x8dca7cdd…b418

0x928dc8…8207

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x18cf3003…51d1

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 0xca841faae5…71486a

← previous block·next block →recent activity