Block #72,571,288

← previous blocknext block →recent activity

Analyzing

Block #72,571,288

13 transactions · 11 stateful · 2026-05-05 10:07:53 UTC

Parallelism

69/100

Blocked

27%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,571,288  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x84fe81bd…607b

0x065c9d…c394

4 touches
1 conflict

0x11d01533…8162

0x065c9d…c394

4 touches
1 conflict

0xccebf4a4…755c

0x065c9d…c394

4 touches
1 conflict

0x9a3af739…c767

0x065c9d…c394

3 touches
1 conflict

0x73cfb748…1b0e

0x065c9d…c394

3 touches
1 conflict

0x5f9ef250…eb12

0x065c9d…c394

3 touches
1 conflict

0x00000000…0015

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity