Block #72,496,959

← previous blocknext block →recent activity

Analyzing

Block #72,496,959

25 transactions · 23 stateful · 2026-05-05 01:53:01 UTC

Parallelism

76/100

Blocked

61%

Avg conflicts / tx

1.08

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,496,959  ·  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

0x00000000…0002

0x7e9d3a…9fda

12 touches
15 conflicts

0x74e71984…ae90

0x2a68ba…90c5

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xb2f67f99…f89f

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x6c6f37ba…c209

0x1b6862…e19c

4 touches
1 conflict

0x60f7fbaf…bd58

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: 0x7e9d3a8a…4f9fda

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity