Block #72,301,339

← previous blocknext block →recent activity

Analyzing

Block #72,301,339

6 transactions · 6 stateful · 2026-05-04 04:09:53 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,301,339  ·  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

0xcfab2ee0…1384

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x04e08304…bb67

0x065c9d…c394

4 touches
1 conflict

0xd56f5c4b…81cb

0x065c9d…c394

3 touches
1 conflict

0x3f8f822e…a890

0x065c9d…c394

3 touches
1 conflict

0x1fab9ed6…41ed

0x065c9d…c394

2 touches
0 conflicts

0xa708f77b…ff5e

0x065c9d…c394

2 touches
0 conflicts

0x1a4b4152…0a08

0x8d0464…4402

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 0xcfab2ee055…ec1384

← previous block·next block →recent activity