Block #72,365,977

← previous blocknext block →recent activity

Analyzing

Block #72,365,977

25 transactions · 18 stateful · 2026-05-04 11:20:26 UTC

Parallelism

72/100

Blocked

56%

Avg conflicts / tx

1.12

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,365,977  ·  25 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

0x0fcd34f4…90e8

0xd32edf…ff58

13 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xe01158fd…f97e

0x1b6862…e19c

6 touches
3 conflicts

0x1c913164…5c2e

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x8d297657…1b03

0x065c9d…c394

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

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

21 conflicts on slot 0x0fcd34f405…1a90e8

← previous block·next block →recent activity