Block #72,225,093

← previous blocknext block →recent activity

Analyzing

Block #72,225,093

11 transactions · 6 stateful · 2026-05-03 19:37:44 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,225,093  ·  11 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

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0fd4b7e7…04ee

0x065c9d…c394

2 touches
0 conflicts

0x1413b528…8a19

0x065c9d…c394

2 touches
0 conflicts

0x551ae5c7…7d63

0x065c9d…c394

2 touches
0 conflicts

0x6eba4796…14af

0x065c9d…c394

2 touches
0 conflicts

0x6f7720db…160d

0x065c9d…c394

2 touches
0 conflicts

0xe5007bc8…6005

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: 0x681e908b…e1ae09

1 conflict on slot 0x0d622e34f9…000000

← previous block·next block →recent activity