Block #73,578,703

← previous blocknext block →recent activity

Analyzing

Block #73,578,703

15 transactions · 12 stateful · 2026-05-10 01:54:19 UTC

Parallelism

60/100

Blocked

42%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,578,703  ·  15 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x22e295f5…1bef

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x02956ce9…f576

0x2ab50b…5c41

2 touches
0 conflicts

0x0375b9c4…455d

0x2ab50b…5c41

2 touches
0 conflicts

0x0a779f88…6e18

0x2ab50b…5c41

2 touches
0 conflicts

0x0be70560…c7e7

0x2ab50b…5c41

2 touches
0 conflicts

0x1035ed1e…3885

0x2ab50b…5c41

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

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity