Block #72,430,806

← previous blocknext block →recent activity

Analyzing

Block #72,430,806

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

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xf0a2835f…40cd

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0ef189a0…d0fc

0x065c9d…c394

2 touches
0 conflicts

0x77834fd2…44b4

0x065c9d…c394

2 touches
0 conflicts

0xa480e389…ff4a

0x065c9d…c394

2 touches
0 conflicts

0xe7b43a2a…c7f5

0x065c9d…c394

2 touches
0 conflicts

0xf9a0ab8e…0338

0x065c9d…c394

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 0xf0a2835f1c…b140cd

← previous block·next block →recent activity