Block #72,859,626

← previous blocknext block →recent activity

Analyzing

Block #72,859,626

13 transactions · 9 stateful · 2026-05-06 18:10:14 UTC

Parallelism

85/100

Blocked

22%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,859,626  ·  13 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

0x2885ce51…3626

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xce7bfe5e…5e58

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0x0f2ba2a8…3e3e

0x065c9d…c394

3 touches
1 conflict

0xc5694de9…ee80

0x065c9d…c394

3 touches
1 conflict

0xe09eda07…8dda

0x2a68ba…90c5

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 0x2885ce511f…b33626

← previous block·next block →recent activity