Block #72,226,485

← previous blocknext block →recent activity

Analyzing

Block #72,226,485

7 transactions · 6 stateful · 2026-05-03 19:47:07 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,226,485  ·  7 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa7e2af84…4341

0x065c9d…c394

4 touches
1 conflict

0xc1960c93…d82e

0x065c9d…c394

3 touches
1 conflict

0x3debf704…a43a

0x065c9d…c394

3 touches
1 conflict

0x653acb35…c64f

0x065c9d…c394

2 touches
0 conflicts

0x962a2ed5…e4fb

0x065c9d…c394

2 touches
0 conflicts

0x972b703a…9082

0x065c9d…c394

2 touches
0 conflicts

0xa215d0ab…5d95

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity