Block #73,483,004

← previous blocknext block →recent activity

Analyzing

Block #73,483,004

16 transactions · 12 stateful · 2026-05-09 15:18:12 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,483,004  ·  16 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

0xb2670b83…54e5

0xd32edf…ff58

7 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

2 touches
0 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

6 conflicts on slot 0xb2670b839d…7254e5

← previous block·next block →recent activity