Block #72,572,532

← previous blocknext block →recent activity

Analyzing

Block #72,572,532

13 transactions · 10 stateful · 2026-05-05 10:16:11 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,572,532  ·  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

0x1807d4fa…3a4d

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x01f0a526…937b

0x065c9d…c394

3 touches
1 conflict

0xb1a8f06a…54c5

0x065c9d…c394

3 touches
1 conflict

0xf5dbfc78…388f

0x065c9d…c394

3 touches
1 conflict

0xec1b7425…0b79

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0x1807d4fab3…fe3a4d

← previous block·next block →recent activity