← previous blocknext block →recent activity

Analyzing

Block #73,463,532

29 transactions · 21 stateful · 2026-05-09 13:08:41 UTC

Parallelism

72/100

Blocked

48%

Avg conflicts / tx

1.07

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,463,532  ·  29 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

0x14bc22fd…bc9c

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0xd53220ed…4734

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

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

28 conflicts on slot 0x14bc22fd3d…d8bc9c

← previous block·next block →recent activity