Block #72,859,617

← previous blocknext block →recent activity

Analyzing

Block #72,859,617

16 transactions · 10 stateful · 2026-05-06 18:10:10 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,859,617  ·  16 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

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0x1ed6c33f…9f9c

0x34b655…2a6f

4 touches
1 conflict

0x316481f7…eec9

0x34b655…2a6f

4 touches
1 conflict

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0x50c2960c…5f37

0x34b655…2a6f

4 touches
1 conflict

0x57eaec15…a582

0x34b655…2a6f

4 touches
1 conflict

0x6f6fc26c…3e34

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