Block #72,430,016

← previous blocknext block →recent activity

Analyzing

Block #72,430,016

20 transactions · 16 stateful · 2026-05-04 18:27:11 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,430,016  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x64dd968f…2caf

0x34b655…2a6f

6 touches
3 conflicts

0x49339736…b223

0x34b655…2a6f

6 touches
3 conflicts

0x02bfdbf9…6514

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x7322fb4a…635b

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00f245ce…1e10

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity