Block #72,271,538

← previous blocknext block →recent activity

Analyzing

Block #72,271,538

11 transactions · 11 stateful · 2026-05-04 00:49:57 UTC

Parallelism

82/100

Blocked

18%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x379cf9a8…f0fa

0x065c9d…c394

4 touches
1 conflict

0x62f52ece…d37d

0x065c9d…c394

4 touches
1 conflict

0x86f469ab…a0b3

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0x7e9d3a…9fda

4 touches
1 conflict

0xc1a3fb68…013f

0x065c9d…c394

3 touches
1 conflict

0x18d2b6c2…2c9e

0x065c9d…c394

3 touches
1 conflict

0x659b4462…d2c6

0x065c9d…c394

3 touches
1 conflict

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 0x379cf9a8d1…eaf0fa

← previous block·next block →recent activity