Block #73,338,841

← previous blocknext block →recent activity

Analyzing

Block #73,338,841

48 transactions · 29 stateful · 2026-05-08 23:18:59 UTC

Parallelism

79/100

Blocked

59%

Avg conflicts / tx

1.21

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,338,841  ·  48 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x76c02ab5…393f

0xd32edf…ff58

19 touches
45 conflicts

0xfac61869…a560

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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 0x76c02ab5fa…b9393f

← previous block·next block →recent activity