Block #73,334,312

← previous blocknext block →recent activity

Analyzing

Block #73,334,312

15 transactions · 13 stateful · 2026-05-08 22:48:54 UTC

Parallelism

60/100

Blocked

38%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,334,312  ·  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

0xf537eaa0…73c8

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x08a80bf5…1b94

0x065c9d…c394

2 touches
0 conflicts

0x303f9621…72b3

0x065c9d…c394

2 touches
0 conflicts

0xb566ba4e…9532

0x065c9d…c394

2 touches
0 conflicts

0xc0fdd223…9999

0x065c9d…c394

2 touches
0 conflicts

0xd4978a8e…dcf7

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: 0x065c9d28…a9c394

15 conflicts on slot 0xf537eaa0c6…3873c8

← previous block·next block →recent activity