Block #72,310,100

← previous blocknext block →recent activity

Analyzing

Block #72,310,100

19 transactions · 15 stateful · 2026-05-04 05:08:16 UTC

Parallelism

74/100

Blocked

53%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,310,100  ·  19 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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

6 touches
3 conflicts

0xe90b3034…c80b

0x34b655…2a6f

5 touches
3 conflicts

0x58799a46…7030

0x34b655…2a6f

4 touches
1 conflict

0x60b8fb2a…61c2

0x34b655…2a6f

4 touches
1 conflict

0x6218cdb8…0852

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity