Block #73,210,475

← previous blocknext block →recent activity

Analyzing

Block #73,210,475

7 transactions · 6 stateful · 2026-05-08 09:05:04 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,210,475  ·  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

0x85698600…d1a5

0x065c9d…c394

4 touches
1 conflict

0xc8009748…694e

0x065c9d…c394

4 touches
1 conflict

0x24a763af…247b

0x065c9d…c394

4 touches
1 conflict

0xd435de59…0128

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xc70adbcf…e46c

0x065c9d…c394

3 touches
1 conflict

0x2f1d9e97…41a6

0x065c9d…c394

3 touches
1 conflict

0x9c5bb81d…bffe

0x065c9d…c394

3 touches
1 conflict

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 0x8569860076…8fd1a5

← previous block·next block →recent activity