Block #72,498,477

← previous blocknext block →recent activity

Analyzing

Block #72,498,477

11 transactions · 10 stateful · 2026-05-05 02:03:07 UTC

Parallelism

82/100

Blocked

10%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,498,477  ·  11 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

0xeedb7e85…ec3b

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6745598d…f2f1

0x065c9d…c394

3 touches
1 conflict

0x80619046…63bb

0x065c9d…c394

3 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x81fd68b0…3589

0x065c9d…c394

2 touches
0 conflicts

0x95c2b808…242f

0x065c9d…c394

2 touches
0 conflicts

0x9999108f…b1a9

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 0xeedb7e854d…38ec3b

← previous block·next block →recent activity