Block #73,651,113

← previous blocknext block →recent activity

Analyzing

Block #73,651,113

11 transactions · 9 stateful · 2026-05-10 09:58:39 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,651,113  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xb91a6f59…722c

0x34b655…2a6f

4 touches
1 conflict

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

0x157b6348…8604

0x34b655…2a6f

2 touches
0 conflicts

0x18978822…2623

0x34b655…2a6f

2 touches
0 conflicts

0x2c539d94…b63a

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0xb91a6f59b9…c8722c

← previous block·next block →recent activity