Block #73,324,459

← previous blocknext block →recent activity

Analyzing

Block #73,324,459

13 transactions · 12 stateful · 2026-05-08 21:43:23 UTC

Parallelism

77/100

Blocked

17%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,324,459  ·  13 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

0xb389d45f…8a4c

0x34b655…2a6f

6 touches
3 conflicts

0x469003d5…3ad3

0x34b655…2a6f

4 touches
1 conflict

0xa2d7d2b2…aa83

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0df6edb4…07fd

0x065c9d…c394

2 touches
0 conflicts

0x1f203465…efa4

0x065c9d…c394

2 touches
0 conflicts

0x68e26026…239e

0x065c9d…c394

2 touches
0 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

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

3 conflicts on slot 0xb389d45f2b…a98a4c

← previous block·next block →recent activity