Block #73,501,007

← previous blocknext block →recent activity

Analyzing

Block #73,501,007

34 transactions · 25 stateful · 2026-05-09 17:18:06 UTC

Parallelism

65/100

Blocked

60%

Avg conflicts / tx

1.21

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,501,007  ·  34 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x9db64d13…fb98

0x34b655…2a6f

16 touches
28 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

16 touches
28 conflicts

0xbfca3cd0…5023

0x34b655…2a6f

16 touches
28 conflicts

0xafd59af5…5257

0xc8689a…ee79

16 touches
28 conflicts

0x2b088f80…4cf9

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

6 touches
3 conflicts

0x1b9e654e…0a08

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

28 conflicts on slot 0x9db64d13f5…6efb98

← previous block·next block →recent activity