Block #72,285,796

← previous blocknext block →recent activity

Analyzing

Block #72,285,796

14 transactions · 13 stateful · 2026-05-04 02:25:47 UTC

Parallelism

57/100

Blocked

46%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,285,796  ·  14 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x47b8e815…9bff

0x065c9d…c394

3 touches
1 conflict

0xd2c3fcd6…f6b9

0x065c9d…c394

3 touches
1 conflict

0x5a54e13e…eaef

0xd32edf…ff58

3 touches
1 conflict

0x0ee68f3b…42ab

0x5afd3e…7620

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

6 conflicts on slot 0xbbee74c2e7…6e567a

← previous block·next block →recent activity