← previous blocknext block →recent activity

Analyzing

Block #101,972,309

21 transactions · 19 stateful · 2026-09-04 18:31:24 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,972,309  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb75367ff…a2b7

0x34b655…2a6f

10 touches
10 conflicts

0x51fc8795…126f

0x34b655…2a6f

10 touches
10 conflicts

0x45082691…dff7

0x34b655…2a6f

8 touches
6 conflicts

0x5746581b…0cb1

0x34b655…2a6f

6 touches
3 conflicts

0x67043b0b…97d7

0x34b655…2a6f

6 touches
3 conflicts

0x7dd96c96…7335

0x34b655…2a6f

6 touches
3 conflicts

0x7e273bc0…5dbc

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

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

10 conflicts on slot 0xb75367ffdb…6fa2b7

← previous block·next block →recent activity