Block #73,599,861

← previous blocknext block →recent activity

Analyzing

Block #73,599,861

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

Parallelism

47/100

Blocked

54%

Avg conflicts / tx

1.53

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,599,861  ·  15 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

0xc6f91b2f…b30f

0x34b655…2a6f

12 touches
15 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x7cbd466f…1700

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x0b28bf77…e53a

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 0xc6f91b2f19…75b30f

← previous block·next block →recent activity