Block #73,348,659

← previous blocknext block →recent activity

Analyzing

Block #73,348,659

19 transactions · 12 stateful · 2026-05-09 00:24:19 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,348,659  ·  19 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

0x06a961fa…f91c

0xd32edf…ff58

11 touches
15 conflicts

0x8d0dfe2c…3345

0x2a68ba…90c5

4 touches
1 conflict

0x198b9103…c89a

0x065c9d…c394

3 touches
1 conflict

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x4dd1db39…a994

0x188d58…ea8e

2 touches
0 conflicts

0x4dd1db39…a995

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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

15 conflicts on slot 0x06a961faa4…6ef91c

← previous block·next block →recent activity