← previous blocknext block →recent activity

Analyzing

Block #101,675,574

18 transactions · 15 stateful · 2026-09-03 17:35:30 UTC

Parallelism

67/100

Blocked

60%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,675,574  ·  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

0xec7dfda7…312b

0x34b655…2a6f

6 touches
3 conflicts

0x2e05467a…e3b3

0x34b655…2a6f

6 touches
3 conflicts

0x340aa314…275b

0x34b655…2a6f

6 touches
3 conflicts

0xe53bd661…5352

0x34b655…2a6f

6 touches
3 conflicts

0x173b64af…6c43

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x5f749304…d1c1

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

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 0xec7dfda7e6…da312b

← previous block·next block →recent activity