Block #73,223,896

← previous blocknext block →recent activity

Analyzing

Block #73,223,896

20 transactions · 15 stateful · 2026-05-08 10:34:23 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,223,896  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbdff944d…447e

0x2a68ba…90c5

8 touches
6 conflicts

0x4687fbf2…8666

0x065c9d…c394

5 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0xc7a2aa38…9d60

0x065c9d…c394

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0xbf121400…5108

0x699abc…6a3b

4 touches
1 conflict

0xd725eb47…d511

0xd32edf…ff58

3 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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xbdff944d20…a2447e

← previous block·next block →recent activity