Block #72,859,962

← previous blocknext block →recent activity

Analyzing

Block #72,859,962

25 transactions · 22 stateful · 2026-05-06 18:12:28 UTC

Parallelism

64/100

Blocked

64%

Avg conflicts / tx

1.64

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,859,962  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xb6264ee6…0e58

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

6 touches
3 conflicts

0x251861eb…78fd

0x34b655…2a6f

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0xdfae454d…8dee

0x065c9d…c394

4 touches
1 conflict

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

28 conflicts on slot 0xb6264ee6a3…d70e58

← previous block·next block →recent activity