Block #72,310,152

← previous blocknext block →recent activity

Analyzing

Block #72,310,152

14 transactions · 13 stateful · 2026-05-04 05:08:37 UTC

Parallelism

64/100

Blocked

38%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,310,152  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbdeb9b39…94cd

0x065c9d…c394

7 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0004

0x5afd3e…7620

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0x4039b31f…0f4a

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xcb643582…2626

0x3bd359…433a

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 0xbdeb9b3903…ad94cd

← previous block·next block →recent activity