← previous blocknext block →recent activity

Analyzing

Block #73,952,810

6 transactions · 6 stateful · 2026-05-11 19:41:12 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,952,810  ·  6 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

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x7d1140c6…14a5

0x34b655…2a6f

4 touches
1 conflict

0xee230b20…5a0f

0x34b655…2a6f

4 touches
1 conflict

0x3bbcdbae…8972

0x34b655…2a6f

2 touches
0 conflicts

0x40b3d30e…7b92

0x34b655…2a6f

2 touches
0 conflicts

0x4dd97522…9468

0x34b655…2a6f

2 touches
0 conflicts

0x5670bd6d…df56

0x34b655…2a6f

2 touches
0 conflicts

0x5b469955…4044

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 0xf853eb8e72…d84027

← previous block·next block →recent activity