← previous blocknext block →recent activity

Analyzing

Block #106,054,236

26 transactions · 22 stateful · 2026-09-19 02:10:00 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,054,236  ·  26 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x309f47c0…e1cf

0x34b655…2a6f

4 touches
1 conflict

0x3b65c5ca…9f83

0x34b655…2a6f

4 touches
1 conflict

0x48828733…fd48

0x34b655…2a6f

4 touches
1 conflict

0x48b6f2c7…2ef7

0x34b655…2a6f

4 touches
1 conflict

0x69d2053b…935a

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

← previous block·next block →recent activity