← previous blocknext block →recent activity

Analyzing

Block #73,647,072

25 transactions · 22 stateful · 2026-05-10 09:31:28 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.84

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,647,072  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc97b3058…4091

0xd32edf…ff58

9 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x08943ea2…ed03

0x754704…b603

6 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x968bdacb…f461

0x2a68ba…90c5

4 touches
1 conflict

0x6af306bb…2e81

0x3bd359…433a

4 touches
1 conflict

0xd77e90ec…8c04

0x3bd359…433a

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

10 conflicts on slot 0xc97b30589c…804091

← previous block·next block →recent activity