← previous blocknext block →recent activity

Analyzing

Block #73,035,122

38 transactions · 28 stateful · 2026-05-07 13:38:17 UTC

Parallelism

79/100

Blocked

61%

Avg conflicts / tx

1.03

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,035,122  ·  38 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

0xd25ad11e…cfb4

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0002

0xd574ca…7ab1

10 touches
10 conflicts

0x69017fce…85c2

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 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

15 conflicts on slot 0xd25ad11e5f…89cfb4

← previous block·next block →recent activity