Block #72,859,676

← previous blocknext block →recent activity

Analyzing

Block #72,859,676

9 transactions · 8 stateful · 2026-05-06 18:10:34 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,859,676  ·  9 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

0xd895ee0b…d301

0x34b655…2a6f

4 touches
1 conflict

0x499adbcf…eb20

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x00bac013…a28c

0x91b81b…6d56

2 touches
0 conflicts

0x9560013d…8caf

0x91b81b…6d56

2 touches
0 conflicts

0x455b104f…3960

0xea1b8e…c5ec

2 touches
0 conflicts

0x535d2f17…3a0f

0xea1b8e…c5ec

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

1 conflict on slot 0xd895ee0be4…14d301

← previous block·next block →recent activity