Block #72,226,101

← previous blocknext block →recent activity

Analyzing

Block #72,226,101

12 transactions · 11 stateful · 2026-05-03 19:44:32 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x55328e52…30b0

0x065c9d…c394

4 touches
1 conflict

0xad739496…9789

0x065c9d…c394

3 touches
1 conflict

0xdca5e1be…f76a

0x065c9d…c394

3 touches
1 conflict

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x42502572…e3a9

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x653acb35…c64f

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