Block #72,430,807

← previous blocknext block →recent activity

Analyzing

Block #72,430,807

12 transactions · 8 stateful · 2026-05-04 18:32:28 UTC

Parallelism

83/100

Blocked

38%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x46d453f2…644b

0x065c9d…c394

4 touches
1 conflict

0xf91e7eda…7777

0x065c9d…c394

4 touches
1 conflict

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0xf54aa8c0…ca09

0x065c9d…c394

3 touches
1 conflict

0xab4ac150…4a5e

0x065c9d…c394

3 touches
1 conflict

0xc24b0101…191e

0x065c9d…c394

3 touches
1 conflict

0x0ec86425…1a53

0x065c9d…c394

3 touches
1 conflict

0x3c35979a…975d

0x34b655…2a6f

2 touches
0 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: 0x065c9d28…a9c394

1 conflict on slot 0x46d453f2a5…0f644b

← previous block·next block →recent activity