← previous blocknext block →recent activity

Analyzing

Block #73,495,959

17 transactions · 14 stateful · 2026-05-09 16:44:27 UTC

Parallelism

82/100

Blocked

36%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,495,959  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x9ea57326…329f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xce9e417e…b413

0x34b655…2a6f

6 touches
3 conflicts

0x4546ebad…b908

0x34b655…2a6f

4 touches
1 conflict

0x1fcacf75…7ade

0x34b655…2a6f

4 touches
1 conflict

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x9ea57326ca…60329f

← previous block·next block →recent activity