Block #72,430,776

← previous blocknext block →recent activity

Analyzing

Block #72,430,776

12 transactions · 9 stateful · 2026-05-04 18:32:15 UTC

Parallelism

83/100

Blocked

44%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,430,776  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0x7e438c85…f897

0x065c9d…c394

4 touches
1 conflict

0xc4e1abb5…57b5

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x0b28bf77…e53a

0x34b655…2a6f

4 touches
1 conflict

0x1319ae2c…7f9a

0x34b655…2a6f

4 touches
1 conflict

0x32ee90db…decc

0x34b655…2a6f

4 touches
1 conflict

0x4f483049…3cc7

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: 0xc8689a47…62ee79

1 conflict on slot 0xc6417de023…802191

← previous block·next block →recent activity