← previous blocknext block →recent activity

Analyzing

Block #73,328,517

16 transactions · 12 stateful · 2026-05-08 22:10:24 UTC

Parallelism

81/100

Blocked

25%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,328,517  ·  16 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

0x90539e2f…6c80

0xd32edf…ff58

5 touches
3 conflicts

0x367350ca…a8cd

0x34b655…2a6f

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x9e719c7a…df63

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0xb91a6f59…722c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa15427f6…d932

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: 0xd32edf66…9fff58

3 conflicts on slot 0x90539e2f30…6e6c80

← previous block·next block →recent activity