Block #73,490,905

← previous blocknext block →recent activity

Analyzing

Block #73,490,905

24 transactions · 18 stateful · 2026-05-09 16:10:55 UTC

Parallelism

67/100

Blocked

56%

Avg conflicts / tx

0.88

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,490,905  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xafd59af5…5257

0xc8689a…ee79

6 touches
3 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

6 touches
3 conflicts

0x893cd52c…5766

0x34b655…2a6f

6 touches
3 conflicts

0x9bbca2b6…184e

0x34b655…2a6f

6 touches
3 conflicts

0x9fd15b84…84c0

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xffedaa84…311b

0x34b655…2a6f

6 touches
3 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: 0x34b6552d…112a6f

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity