← previous blocknext block →recent activity

Analyzing

Block #72,300,763

26 transactions · 17 stateful · 2026-05-04 04:06:03 UTC

Parallelism

73/100

Blocked

65%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,300,763  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x1bf14693…8f13

0x065c9d…c394

6 touches
3 conflicts

0xf823e97f…2ee6

0x065c9d…c394

6 touches
3 conflicts

0x8dd5b918…916a

0xd32edf…ff58

5 touches
3 conflicts

0xeb673994…b86e

0x065c9d…c394

4 touches
1 conflict

0xce143411…a324

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: 0x065c9d28…a9c394

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity