Block #73,210,258

← previous blocknext block →recent activity

Analyzing

Block #73,210,258

12 transactions · 11 stateful · 2026-05-08 09:03:37 UTC

Parallelism

58/100

Blocked

45%

Avg conflicts / tx

0.92

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,210,258  ·  12 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x48a9b0fa…ff96

0xd32edf…ff58

9 touches
10 conflicts

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0xf4730a2d…3538

0x34b655…2a6f

4 touches
1 conflict

0xf7fa2c79…ca59

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x083a8763…5a7b

0x1b6862…e19c

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

10 conflicts on slot 0x48a9b0faec…bdff96

← previous block·next block →recent activity