← previous blocknext block →recent activity

Analyzing

Block #72,974,790

26 transactions · 17 stateful · 2026-05-07 06:56:42 UTC

Parallelism

73/100

Blocked

47%

Avg conflicts / tx

0.96

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,974,790  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xe589c635…559e

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x70b2f813…783c

0x2a68ba…90c5

8 touches
6 conflicts

0x3a3097d7…2ab8

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

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: 0xd32edf66…9fff58

21 conflicts on slot 0xe589c635cb…c3559e

← previous block·next block →recent activity