Block #73,598,430

← previous blocknext block →recent activity

Analyzing

Block #73,598,430

12 transactions · 11 stateful · 2026-05-10 04:05:30 UTC

Parallelism

75/100

Blocked

27%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,598,430  ·  12 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x489750d8…22c3

0x065c9d…c394

2 touches
0 conflicts

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0xcd5417e6…1963

0x065c9d…c394

2 touches
0 conflicts

0x00000000…009a

0x16f70c…c3dd

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity