← previous blocknext block →recent activity

Analyzing

Block #73,751,789

19 transactions · 16 stateful · 2026-05-10 21:17:59 UTC

Parallelism

53/100

Blocked

50%

Avg conflicts / tx

1.53

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,751,789  ·  19 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x5de96bd3…c60c

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x2d975111…5f52

0x34b655…2a6f

10 touches
10 conflicts

0x5d70606a…1d53

0x34b655…2a6f

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x45b9e08c…a11b

0x34b655…2a6f

6 touches
3 conflicts

0x57de3828…3fbb

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

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

21 conflicts on slot 0x5de96bd34a…ecc60c

← previous block·next block →recent activity