Block #72,301,300

← previous blocknext block →recent activity

Analyzing

Block #72,301,300

6 transactions · 5 stateful · 2026-05-04 04:09:37 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x8a1abe13…9188

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7c759cc5…8525

0x065c9d…c394

4 touches
1 conflict

0x29658512…dfa5

0x065c9d…c394

3 touches
1 conflict

0x2d11f8d1…ade0

0x065c9d…c394

3 touches
1 conflict

0x540b21aa…47bb

0x065c9d…c394

2 touches
0 conflicts

0xf5dc4bbf…c7ba

0x065c9d…c394

2 touches
0 conflicts

0xf823e97f…2ee6

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 0x8a1abe1379…9b9188

← previous block·next block →recent activity