← previous blocknext block →recent activity

Analyzing

Block #101,955,146

21 transactions · 18 stateful · 2026-09-04 17:04:29 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,955,146  ·  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

0x898a08aa…c855

0x34b655…2a6f

6 touches
3 conflicts

0x477cb4f5…11b4

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x1a2e73cf…5ff5

0x34b655…2a6f

6 touches
3 conflicts

0x024b482b…16b0

0x34b655…2a6f

6 touches
3 conflicts

0x810322e4…4f6b

0x34b655…2a6f

6 touches
3 conflicts

0x8e33015d…b134

0x34b655…2a6f

5 touches
3 conflicts

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 0x898a08aa11…0cc855

← previous block·next block →recent activity