Block #72,285,835

← previous blocknext block →recent activity

Analyzing

Block #72,285,835

27 transactions · 24 stateful · 2026-05-04 02:26:03 UTC

Parallelism

74/100

Blocked

63%

Avg conflicts / tx

1.33

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,285,835  ·  27 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

0xb68d8ed4…e69e

0xd32edf…ff58

9 touches
10 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

6 touches
3 conflicts

0xe072d43a…1835

0x34b655…2a6f

6 touches
3 conflicts

0xac79a0c7…be0f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

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

10 conflicts on slot 0xb68d8ed41d…0be69e

← previous block·next block →recent activity