← previous blocknext block →recent activity

Analyzing

Block #73,808,591

9 transactions · 9 stateful · 2026-05-11 03:40:49 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,808,591  ·  9 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

0xa486f342…64d5

0x34b655…2a6f

4 touches
1 conflict

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0x7a015069…3648

0x123468…4321

2 touches
0 conflicts

0xfed18a3e…0a02

0x188d58…ea8e

2 touches
0 conflicts

0xfed18a3e…0a03

0x188d58…ea8e

2 touches
0 conflicts

0x1b5d2e60…99b5

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 0xa486f34281…4664d5

← previous block·next block →recent activity