Block #72,394,866

← previous blocknext block →recent activity

Analyzing

Block #72,394,866

6 transactions · 5 stateful · 2026-05-04 14:32:59 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,394,866  ·  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

0x2b42047a…c15c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8a4e5e0b…1014

0x065c9d…c394

3 touches
1 conflict

0x3274ad72…9df8

0x065c9d…c394

2 touches
0 conflicts

0x34bb851e…8cac

0x065c9d…c394

2 touches
0 conflicts

0x37768a7d…f268

0x065c9d…c394

2 touches
0 conflicts

0x455a488a…0e52

0x065c9d…c394

2 touches
0 conflicts

0x48c6e5aa…cc95

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 0x2b42047a35…e0c15c

← previous block·next block →recent activity