Block #72,860,255

← previous blocknext block →recent activity

Analyzing

Block #72,860,255

12 transactions · 10 stateful · 2026-05-06 18:14:25 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,860,255  ·  12 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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x78e3ec57…8bf9

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xeef10d5b…295a

0xd32edf…ff58

3 touches
1 conflict

0x35ae33a1…bdcb

0x065c9d…c394

2 touches
0 conflicts

0x7d82eb22…7b31

0x065c9d…c394

2 touches
0 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

2 touches
0 conflicts

0xda705de4…8d3d

0x065c9d…c394

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

← previous block·next block →recent activity