Block #73,035,698

← previous blocknext block →recent activity

Analyzing

Block #73,035,698

31 transactions · 22 stateful · 2026-05-07 13:42:07 UTC

Parallelism

55/100

Blocked

59%

Avg conflicts / tx

2.94

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #73,035,698  ·  31 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

0x527d1ad7…51d2

0xd32edf…ff58

27 touches
91 conflicts

0x00000000…002f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xe783dfa4…549a

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

91 conflicts on slot 0x527d1ad766…8951d2

← previous block·next block →recent activity