Block #73,681,233

← previous blocknext block →recent activity

Analyzing

Block #73,681,233

38 transactions · 26 stateful · 2026-05-10 13:21:59 UTC

Parallelism

79/100

Blocked

54%

Avg conflicts / tx

0.82

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,681,233  ·  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

0x0ac31945…2c72

0x065c9d…c394

10 touches
10 conflicts

0xf5836488…f3f6

0xd32edf…ff58

9 touches
10 conflicts

0x3e733ae4…4598

0x34b655…2a6f

8 touches
6 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

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: 0x065c9d28…a9c394

10 conflicts on slot 0x0ac3194537…8f2c72

← previous block·next block →recent activity