Block #73,599,888

← previous blocknext block →recent activity

Analyzing

Block #73,599,888

7 transactions · 4 stateful · 2026-05-10 04:15:14 UTC

Parallelism

71/100

Blocked

25%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,599,888  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x51e1366d…7f1d

0x065c9d…c394

2 touches
0 conflicts

0x76c5d5c9…945c

0x065c9d…c394

2 touches
0 conflicts

0x97a7a85c…ba1b

0x065c9d…c394

2 touches
0 conflicts

0xd80e3744…c051

0x065c9d…c394

2 touches
0 conflicts

0xf7bde180…b009

0x065c9d…c394

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity