← previous blocknext block →recent activity

Analyzing

Block #73,650,956

23 transactions · 19 stateful · 2026-05-10 09:57:36 UTC

Parallelism

70/100

Blocked

58%

Avg conflicts / tx

1.26

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,650,956  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc30d5bee…0bc1

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c2

0x1b6862…e19c

6 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

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

21 conflicts on slot 0xc30d5bee61…310bc1

← previous block·next block →recent activity