Block #72,395,033

← previous blocknext block →recent activity

Analyzing

Block #72,395,033

11 transactions · 9 stateful · 2026-05-04 14:34:06 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,395,033  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0x7e9d3a…9fda

4 touches
1 conflict

0x4103e62a…c388

0x065c9d…c394

4 touches
1 conflict

0x5475b36a…331a

0x065c9d…c394

2 touches
0 conflicts

0xb2a0d36e…1799

0x065c9d…c394

2 touches
0 conflicts

0xd0e2fd6a…5379

0x065c9d…c394

2 touches
0 conflicts

0xe9494884…9cbd

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 0x0000000000…00003d

← previous block·next block →recent activity