← previous blocknext block →recent activity

Analyzing

Block #101,853,453

17 transactions · 17 stateful · 2026-09-04 08:30:12 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,853,453  ·  17 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

0xf5d28bce…c32c

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x9bff3222…a246

0x34b655…2a6f

6 touches
3 conflicts

0x9c088939…ddd7

0x34b655…2a6f

6 touches
3 conflicts

0xb3e293fe…be2e

0x34b655…2a6f

6 touches
3 conflicts

0xb73a5ffd…ddee

0x34b655…2a6f

6 touches
3 conflicts

0xc0f6895c…e428

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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 0xf5d28bce28…fbc32c

← previous block·next block →recent activity