Block #72,370,718

← previous blocknext block →recent activity

Analyzing

Block #72,370,718

6 transactions · 6 stateful · 2026-05-04 11:52:00 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,370,718  ·  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

0x502abd89…1251

0x065c9d…c394

4 touches
1 conflict

0xc6113171…6369

0x065c9d…c394

4 touches
1 conflict

0x5daef492…4dc9

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbdceb641…cf1e

0x065c9d…c394

3 touches
1 conflict

0x6a4e85fc…0252

0x065c9d…c394

3 touches
1 conflict

0x1d3bf951…b710

0x065c9d…c394

3 touches
1 conflict

0x6148ac38…37cb

0x065c9d…c394

3 touches
1 conflict

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 0x502abd89e8…dc1251

← previous block·next block →recent activity