Block #73,343,653

← previous blocknext block →recent activity

Analyzing

Block #73,343,653

29 transactions · 21 stateful · 2026-05-08 23:51:00 UTC

Parallelism

62/100

Blocked

52%

Avg conflicts / tx

1.66

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,343,653  ·  29 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x68aadc55…9bd5

0xd32edf…ff58

19 touches
45 conflicts

0xba5743c7…21c4

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 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

45 conflicts on slot 0x68aadc55ef…8a9bd5

← previous block·next block →recent activity