Block #73,333,886

← previous blocknext block →recent activity

Analyzing

Block #73,333,886

10 transactions · 8 stateful · 2026-05-08 22:46:04 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,333,886  ·  10 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

0x2e2214a9…fe0d

0xaba216…a862

4 touches
1 conflict

0xd821ae10…fe17

0xc8689a…ee79

4 touches
1 conflict

0x0175b7a6…1dbe

0xaba216…a862

3 touches
1 conflict

0x0c89ea7e…13eb

0xaba216…a862

3 touches
1 conflict

0xfefb1061…f78c

0x065c9d…c394

3 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

2 touches
0 conflicts

0xfcd17a98…e3ce

0x065c9d…c394

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