← previous blocknext block →recent activity

Analyzing

Block #73,495,617

16 transactions · 13 stateful · 2026-05-09 16:42:10 UTC

Parallelism

75/100

Blocked

31%

Avg conflicts / tx

0.31

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,495,617  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf49e7433…f1cc

0xd32edf…ff58

5 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x4dd1db39…a994

0x188d58…ea8e

4 touches
1 conflict

0x4dd1db39…a996

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb80

0x1b6862…e19c

4 touches
1 conflict

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0x6ebb5837…ebb8

0x754704…b603

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: 0xd32edf66…9fff58

3 conflicts on slot 0xf49e7433e9…14f1cc

← previous block·next block →recent activity