Block #72,496,774

← previous blocknext block →recent activity

Analyzing

Block #72,496,774

14 transactions · 11 stateful · 2026-05-05 01:51:46 UTC

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,496,774  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x6423fcab…a7c1

0x34b655…2a6f

6 touches
3 conflicts

0x9e0e23b5…6910

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xf8f1e808…a4fd

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x9b8800c1…ed12

0x34b655…2a6f

4 touches
1 conflict

0x00000000…002c

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: 0x34b6552d…112a6f

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity