← previous blocknext block →recent activity

Analyzing

Block #101,854,147

18 transactions · 15 stateful · 2026-09-04 08:33:41 UTC

Parallelism

67/100

Blocked

60%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,854,147  ·  18 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

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0x0ec07cf7…c0c9

0x34b655…2a6f

6 touches
3 conflicts

0x18860aca…0f33

0x34b655…2a6f

6 touches
3 conflicts

0x4f3cc09a…2804

0x34b655…2a6f

6 touches
3 conflicts

0x79ec4509…1f61

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x95bf55e1…e0a7

0x34b655…2a6f

6 touches
3 conflicts

0xf5d28bce…c32c

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

6 conflicts on slot 0x51fc8795c8…57126f

← previous block·next block →recent activity