Block #72,394,739

← previous blocknext block →recent activity

Analyzing

Block #72,394,739

8 transactions · 7 stateful · 2026-05-04 14:32:08 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,394,739  ·  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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0xf167de18…637c

0x065c9d…c394

3 touches
1 conflict

0x4285a46e…3f74

0x065c9d…c394

3 touches
1 conflict

0xb8ddd545…2d82

0x065c9d…c394

2 touches
0 conflicts

0xea4fbdc7…bd59

0x065c9d…c394

2 touches
0 conflicts

0xf78b4ef3…a7a7

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity