Block #72,314,645

← previous blocknext block →recent activity

Analyzing

Block #72,314,645

14 transactions · 13 stateful · 2026-05-04 05:38:30 UTC

Parallelism

64/100

Blocked

54%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,314,645  ·  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

0xbb975a6c…bff4

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2484cc15…5afc

0x34b655…2a6f

4 touches
1 conflict

0x5301770c…2ac8

0x34b655…2a6f

4 touches
1 conflict

0x60000fb6…6083

0x34b655…2a6f

4 touches
1 conflict

0x6a4d7604…6324

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 0xbb975a6cb4…7fbff4

← previous block·next block →recent activity