Block #73,334,464

← previous blocknext block →recent activity

Analyzing

Block #73,334,464

14 transactions · 13 stateful · 2026-05-08 22:49:53 UTC

Parallelism

86/100

Blocked

23%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x3a2ed7ab…0414

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x7952cec3…d693

0x065c9d…c394

3 touches
1 conflict

0xa049215d…8526

0x065c9d…c394

3 touches
1 conflict

0x6eba5e7f…4b52

0x34b655…2a6f

2 touches
0 conflicts

0x908d4442…2c4b

0x34b655…2a6f

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 0x3a2ed7ab06…a20414

← previous block·next block →recent activity