Block #73,201,644

← previous blocknext block →recent activity

Analyzing

Block #73,201,644

14 transactions · 13 stateful · 2026-05-08 08:06:19 UTC

Parallelism

64/100

Blocked

31%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,201,644  ·  14 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

0xf3d65d70…d7c8

0xd32edf…ff58

9 touches
10 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x375791c9…fa70

0x065c9d…c394

2 touches
0 conflicts

0x7d6e4a5b…6a9c

0x065c9d…c394

2 touches
0 conflicts

0x7f189cf6…afab

0x065c9d…c394

2 touches
0 conflicts

0xa61fd549…3da0

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: 0xd32edf66…9fff58

10 conflicts on slot 0xf3d65d7091…aad7c8

← previous block·next block →recent activity