← previous blocknext block →recent activity

Analyzing

Block #73,651,429

11 transactions · 9 stateful · 2026-05-10 10:00:46 UTC

Parallelism

64/100

Blocked

44%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,651,429  ·  11 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

0x9d3679a0…4411

0xd32edf…ff58

7 touches
6 conflicts

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x7f81fb82…633e

0x065c9d…c394

2 touches
0 conflicts

0xab489a22…c481

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

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

6 conflicts on slot 0x9d3679a093…a64411

← previous block·next block →recent activity