Block #72,271,862

← previous blocknext block →recent activity

Analyzing

Block #72,271,862

8 transactions · 8 stateful · 2026-05-04 00:52:07 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,271,862  ·  8 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

0xcfd3345a…6713

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6cefa72f…e938

0x065c9d…c394

3 touches
1 conflict

0xc9661afa…4a30

0x065c9d…c394

3 touches
1 conflict

0x56882c39…e4db

0x065c9d…c394

2 touches
0 conflicts

0x9b21d8b5…f44d

0x065c9d…c394

2 touches
0 conflicts

0xa8109a3f…e98f

0x065c9d…c394

2 touches
0 conflicts

0xdd3bfb55…6e69

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 0xcfd3345af1…936713

← previous block·next block →recent activity