Block #72,399,912

← previous blocknext block →recent activity

Analyzing

Block #72,399,912

8 transactions · 8 stateful · 2026-05-04 15:06:38 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,399,912  ·  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

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xac44a909…00ff

0x065c9d…c394

3 touches
1 conflict

0xf6c6daa4…a93d

0x065c9d…c394

3 touches
1 conflict

0x5d8ff855…bd5c

0x065c9d…c394

2 touches
0 conflicts

0x7abf1904…b003

0x065c9d…c394

2 touches
0 conflicts

0x9a3fd26c…03f7

0x065c9d…c394

2 touches
0 conflicts

0xd2adf20e…2994

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 0xbbee74c2e7…6e567a

← previous block·next block →recent activity