Block #72,429,300

← previous blocknext block →recent activity

Analyzing

Block #72,429,300

33 transactions · 25 stateful · 2026-05-04 18:22:25 UTC

Parallelism

79/100

Blocked

52%

Avg conflicts / tx

0.76

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,429,300  ·  33 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

0xe1fd24a0…eaa6

0x34b655…2a6f

10 touches
10 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

8 touches
6 conflicts

0xafd59af5…5257

0xc8689a…ee79

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

8 touches
6 conflicts

0x73d79459…9c01

0x34b655…2a6f

8 touches
6 conflicts

0x2484cc15…5afc

0x34b655…2a6f

8 touches
6 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

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

10 conflicts on slot 0xe1fd24a00e…feeaa6

← previous block·next block →recent activity