Block #73,694,875

← previous blocknext block →recent activity

Analyzing

Block #73,694,875

15 transactions · 15 stateful · 2026-05-10 14:53:54 UTC

Parallelism

53/100

Blocked

53%

Avg conflicts / tx

1.6

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,694,875  ·  15 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xa91c899f…6ee3

0x34b655…2a6f

12 touches
15 conflicts

0x14845934…d13c

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

0x9be2b99a…a959

0x34b655…2a6f

6 touches
3 conflicts

0x23951077…539b

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 0xa91c899f02…fa6ee3

← previous block·next block →recent activity