Block #72,285,750

← previous blocknext block →recent activity

Analyzing

Block #72,285,750

43 transactions · 29 stateful · 2026-05-04 02:25:29 UTC

Parallelism

77/100

Blocked

55%

Avg conflicts / tx

1.02

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #72,285,750  ·  43 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xbf80a071…023b

0xd32edf…ff58

15 touches
28 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

10 touches
10 conflicts

0xbb6c6d82…6205

0x065c9d…c394

9 touches
10 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

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: 0xd32edf66…9fff58

28 conflicts on slot 0xbf80a07152…82023b

← previous block·next block →recent activity