Block #72,425,818

← previous blocknext block →recent activity

Analyzing

Block #72,425,818

30 transactions · 18 stateful · 2026-05-04 17:59:17 UTC

Parallelism

63/100

Blocked

56%

Avg conflicts / tx

1.83

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #72,425,818  ·  30 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xfa53fb9d…30e3

0xd32edf…ff58

21 touches
55 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…0008

0x2f83f2…9c4d

2 touches
0 conflicts

0x23951077…539b

0x34b655…2a6f

2 touches
0 conflicts

0x313f2565…5b00

0x34b655…2a6f

2 touches
0 conflicts

0x4f483049…3cc7

0x34b655…2a6f

2 touches
0 conflicts

0x50c2960c…5f37

0x34b655…2a6f

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

55 conflicts on slot 0xfa53fb9d9e…5e30e3

← previous block·next block →recent activity