← previous blocknext block →recent activity

Analyzing

Block #101,935,402

26 transactions · 25 stateful · 2026-09-04 15:24:15 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,935,402  ·  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

0x076cd4ce…f9c8

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x67043b0b…97d7

0x34b655…2a6f

6 touches
3 conflicts

0x67c1f465…38b3

0x34b655…2a6f

6 touches
3 conflicts

0x7e273bc0…5dbc

0x34b655…2a6f

6 touches
3 conflicts

0x897879a1…9c78

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0xa7e3ddfa…f0c7

0x34b655…2a6f

6 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 0x076cd4ce6f…48f9c8

← previous block·next block →recent activity