Block #73,200,422

← previous blocknext block →recent activity

Analyzing

Block #73,200,422

10 transactions · 10 stateful · 2026-05-08 07:58:11 UTC

Parallelism

80/100

Blocked

10%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,200,422  ·  10 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

0x699abc…6a3b

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xb7a19b6b…2ffa

0x699abc…6a3b

3 touches
1 conflict

0x1a6233df…104b

0x699abc…6a3b

3 touches
1 conflict

0x1a6233df…104a

0x699abc…6a3b

3 touches
1 conflict

0xb7a19b6b…2ff9

0x699abc…6a3b

3 touches
1 conflict

0x2f77f0f6…4a92

0x188d58…ea8e

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: 0x699abc15…c86a3b

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity