Block #72,283,376

← previous blocknext block →recent activity

Analyzing

Block #72,283,376

11 transactions · 9 stateful · 2026-05-04 02:09:30 UTC

Parallelism

64/100

Blocked

33%

Avg conflicts / tx

0.73

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,283,376  ·  11 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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0xbbee74c2…567a

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x3e62b818…8be9

0x065c9d…c394

2 touches
0 conflicts

0xb1a37e55…c17e

0x065c9d…c394

2 touches
0 conflicts

0x00000000…000b

0x24b8be…7f9e

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x00000000…0004

0xd0f8a6…badc

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity