← previous blocknext block →recent activity

Analyzing

Block #73,751,605

12 transactions · 10 stateful · 2026-05-10 21:16:45 UTC

Parallelism

58/100

Blocked

40%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,751,605  ·  12 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x45b9e08c…a11b

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

8 touches
6 conflicts

0x57de3828…3fbb

0x34b655…2a6f

6 touches
3 conflicts

0x129ba946…48ab

0x34b655…2a6f

6 touches
3 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

6 touches
3 conflicts

0xd49762c9…1359

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity