Block #72,394,971

← previous blocknext block →recent activity

Analyzing

Block #72,394,971

10 transactions · 10 stateful · 2026-05-04 14:33:41 UTC

Parallelism

70/100

Blocked

30%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,394,971  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x965b4e32…0c5f

0x065c9d…c394

4 touches
1 conflict

0xb1f3a72e…3a5c

0x065c9d…c394

3 touches
1 conflict

0xc193cd6f…a35a

0x065c9d…c394

3 touches
1 conflict

0xa1fff0d8…2bce

0x065c9d…c394

2 touches
0 conflicts

0xbde72e37…8a90

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity