Block #73,261,266

← previous blocknext block →recent activity

Analyzing

Block #73,261,266

33 transactions · 22 stateful · 2026-05-08 14:42:46 UTC

Parallelism

58/100

Blocked

64%

Avg conflicts / tx

2.79

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #73,261,266  ·  33 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

0x7cbb0201…8c0c

0xd32edf…ff58

27 touches
91 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001c

0x1b6862…e19c

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

91 conflicts on slot 0x7cbb020166…0b8c0c

← previous block·next block →recent activity