← previous blocknext block →recent activity

Analyzing

Block #73,697,311

20 transactions · 17 stateful · 2026-05-10 15:10:18 UTC

Parallelism

75/100

Blocked

53%

Avg conflicts / tx

0.85

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,697,311  ·  20 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

0x44de0da8…444d

0xd32edf…ff58

9 touches
10 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xe783dfa4…5497

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

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

10 conflicts on slot 0x44de0da8ce…15444d

← previous block·next block →recent activity