Block #72,284,402

← previous blocknext block →recent activity

Analyzing

Block #72,284,402

14 transactions · 11 stateful · 2026-05-04 02:16:23 UTC

Parallelism

86/100

Blocked

18%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,284,402  ·  14 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

0xe532957e…7fa1

0x065c9d…c394

4 touches
1 conflict

0xf69463e8…ddff

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1a5e1e38…f7a5

0x065c9d…c394

3 touches
1 conflict

0x7da0d583…797d

0x065c9d…c394

3 touches
1 conflict

0xfc9d4f30…4bb2

0x065c9d…c394

3 touches
1 conflict

0x2fda44b8…6c26

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 0xe532957e55…887fa1

← previous block·next block →recent activity