Block #72,425,679

← previous blocknext block →recent activity

Analyzing

Block #72,425,679

22 transactions · 15 stateful · 2026-05-04 17:58:21 UTC

Parallelism

64/100

Blocked

47%

Avg conflicts / tx

0.82

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,425,679  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

6 touches
3 conflicts

0x2528e717…2a22

0x34b655…2a6f

6 touches
3 conflicts

0x5268df0f…c3d1

0x34b655…2a6f

4 touches
1 conflict

0x55671be1…2bc9

0x34b655…2a6f

4 touches
1 conflict

0x5d30061d…27e7

0x34b655…2a6f

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

6 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity