Block #72,430,542

← previous blocknext block →recent activity

Analyzing

Block #72,430,542

6 transactions · 6 stateful · 2026-05-04 18:30:42 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x31e9ff2a…7dba

0x065c9d…c394

2 touches
0 conflicts

0x3c24887c…2eb7

0x065c9d…c394

2 touches
0 conflicts

0x53931041…7060

0x065c9d…c394

2 touches
0 conflicts

0xb96a4937…d4b5

0x065c9d…c394

2 touches
0 conflicts

0xe3083bbd…af65

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 0x0000000000…00003d

← previous block·next block →recent activity