Block #73,464,489

← previous blocknext block →recent activity

Analyzing

Block #73,464,489

10 transactions · 9 stateful · 2026-05-09 13:15:04 UTC

Parallelism

60/100

Blocked

44%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,464,489  ·  10 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x031569a0…40db

0x065c9d…c394

4 touches
1 conflict

0x28e2627e…3717

0x065c9d…c394

4 touches
1 conflict

0x443ec8dc…445d

0x065c9d…c394

4 touches
1 conflict

0xf8da7134…63f2

0x065c9d…c394

3 touches
1 conflict

0x87e5b55f…02a9

0x065c9d…c394

3 touches
1 conflict

0xc0115b84…b11a

0x065c9d…c394

3 touches
1 conflict

0x7a01808b…e5ab

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity