Block #73,333,663

← previous blocknext block →recent activity

Analyzing

Block #73,333,663

13 transactions · 12 stateful · 2026-05-08 22:44:35 UTC

Parallelism

85/100

Blocked

17%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,333,663  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x267a4613…3f58

0xd32edf…ff58

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x4dd1db39…a994

0x188d58…ea8e

2 touches
0 conflicts

0x4dd1db39…a996

0x188d58…ea8e

2 touches
0 conflicts

0xe8adf936…34b0

0x188d58…ea8e

2 touches
0 conflicts

0xe8adf936…34b2

0x188d58…ea8e

2 touches
0 conflicts

0xf60bb017…fc20

0x188d58…ea8e

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity