← previous blocknext block →recent activity

Analyzing

Block #106,100,821

21 transactions · 19 stateful · 2026-09-19 06:04:27 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #106,100,821  ·  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

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x087ef620…186e

0x6f6493…b480

4 touches
1 conflict

0x0c3b360a…c083

0x6f6493…b480

4 touches
1 conflict

0x0d3cd62c…d4ef

0x6f6493…b480

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 0x51fc8795c8…57126f

← previous block·next block →recent activity