Block #72,285,964

← previous blocknext block →recent activity

Analyzing

Block #72,285,964

21 transactions · 18 stateful · 2026-05-04 02:26:55 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,285,964  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xe54a1f6f…18f2

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0xd7a2b02f…1da4

0x34b655…2a6f

6 touches
3 conflicts

0xfc72cde2…efc0

0xd32edf…ff58

5 touches
3 conflicts

0x257251ca…49b8

0x34b655…2a6f

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

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: 0x34b6552d…112a6f

10 conflicts on slot 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity