← previous blocknext block →recent activity

Analyzing

Block #73,804,851

18 transactions · 11 stateful · 2026-05-11 03:15:52 UTC

Parallelism

67/100

Blocked

64%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,804,851  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x44db0664…bd82

0xd32edf…ff58

11 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x33018431…8f5e

0x188d58…ea8e

4 touches
1 conflict

0x56a919c4…ab49

0xe7cd86…c82d

4 touches
1 conflict

0x33018431…8f5c

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0003

0x942644…91ab

4 touches
1 conflict

0x00000000…0004

0x942644…91ab

4 touches
1 conflict

0x00000000…0012

0x942644…91ab

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

15 conflicts on slot 0x44db0664c4…e4bd82

← previous block·next block →recent activity