← previous blocknext block →recent activity

Analyzing

Block #73,493,275

28 transactions · 24 stateful · 2026-05-09 16:26:38 UTC

Parallelism

71/100

Blocked

58%

Avg conflicts / tx

1.64

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,493,275  ·  28 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x48b74f0f…3d67

0xd32edf…ff58

15 touches
28 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

8 touches
6 conflicts

0x17a7f697…dcb1

0x1b6862…e19c

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0000

0x63e48b…53f2

8 touches
6 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

28 conflicts on slot 0x48b74f0f61…c53d67

← previous block·next block →recent activity