Block #72,285,939

← previous blocknext block →recent activity

Analyzing

Block #72,285,939

25 transactions · 15 stateful · 2026-05-04 02:26:45 UTC

Parallelism

76/100

Blocked

60%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,285,939  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xdba672a3…866a

0xd32edf…ff58

11 touches
15 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x3800b41b…8916

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

2 touches
0 conflicts

0xfe3bddd2…8b48

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0003

0x5afd3e…7620

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: 0xd32edf66…9fff58

15 conflicts on slot 0xdba672a330…3f866a

← previous block·next block →recent activity