Block #73,647,268

← previous blocknext block →recent activity

Analyzing

Block #73,647,268

13 transactions · 11 stateful · 2026-05-10 09:32:47 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,647,268  ·  13 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

0x8a2657f5…e008

0x34b655…2a6f

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0xdbadf6b0…43b2

0x33176b…e078

2 touches
0 conflicts

0x2c539d94…b63a

0x34b655…2a6f

2 touches
0 conflicts

0xac206e47…ef7d

0x34b655…2a6f

2 touches
0 conflicts

0xb82bffbd…c6de

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 0x8a2657f5c3…4ce008

← previous block·next block →recent activity