← previous blocknext block →recent activity

Analyzing

Block #73,049,671

30 transactions · 27 stateful · 2026-05-07 15:15:12 UTC

Parallelism

73/100

Blocked

48%

Avg conflicts / tx

1.17

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,049,671  ·  30 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x0f19aebe…5de5

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…001f

0x1b6862…e19c

8 touches
6 conflicts

0x251861eb…78fd

0x34b655…2a6f

8 touches
6 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x8e66da19…66b6

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

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 0x0f19aebea7…a85de5

← previous block·next block →recent activity