Block #73,211,715

← previous blocknext block →recent activity

Analyzing

Block #73,211,715

29 transactions · 26 stateful · 2026-05-08 09:13:15 UTC

Parallelism

55/100

Blocked

65%

Avg conflicts / tx

2.55

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,211,715  ·  29 txs across 13 waves  ·  depth 13
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

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

0xa8fbb046…b5f1

0xd32edf…ff58

19 touches
45 conflicts

0x7f189cf6…afab

0x065c9d…c394

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

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

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

45 conflicts on slot 0xa8fbb04689…b6b5f1

← previous block·next block →recent activity