← previous blocknext block →recent activity

Analyzing

Block #73,476,429

14 transactions · 11 stateful · 2026-05-09 14:34:30 UTC

Parallelism

79/100

Blocked

27%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,476,429  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x158bac4e…0c89

0x065c9d…c394

2 touches
0 conflicts

0x2e4499b9…6d34

0x065c9d…c394

2 touches
0 conflicts

0x3c6ab467…82b2

0x065c9d…c394

2 touches
0 conflicts

0x3e1c59c7…6906

0x065c9d…c394

2 touches
0 conflicts

0x63bc4a18…c06a

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

3 conflicts on slot 0x0d622e34f9…000000

← previous block·next block →recent activity