Block #73,334,484

← previous blocknext block →recent activity

Analyzing

Block #73,334,484

10 transactions · 9 stateful · 2026-05-08 22:50:00 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,334,484  ·  10 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

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd821ae10…fe17

0xc8689a…ee79

4 touches
1 conflict

0x0175b7a6…1db9

0xaba216…a862

4 touches
1 conflict

0x0175b7a6…1dba

0xaba216…a862

4 touches
1 conflict

0x0175b7a6…1dbb

0xaba216…a862

4 touches
1 conflict

0x0ef1e663…8f2a

0xaba216…a862

4 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

3 conflicts on slot 0x6f08361da9…89bda6

← previous block·next block →recent activity