← previous blocknext block →recent activity

Analyzing

Block #73,698,327

13 transactions · 9 stateful · 2026-05-10 15:17:10 UTC

Parallelism

62/100

Blocked

44%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,698,327  ·  13 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

0x5be89a5b…fa68

0xd32edf…ff58

7 touches
6 conflicts

0x80eef0a5…ef42

0x065c9d…c394

6 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

6 touches
3 conflicts

0x73912233…4586

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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

6 conflicts on slot 0x5be89a5bda…bdfa68

← previous block·next block →recent activity