← previous blocknext block →recent activity

Analyzing

Block #73,660,320

32 transactions · 27 stateful · 2026-05-10 11:00:39 UTC

Parallelism

78/100

Blocked

56%

Avg conflicts / tx

1.22

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,660,320  ·  32 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

0x00000000…0002

0xab3526…fa38

14 touches
21 conflicts

0x38524fae…9deb

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0xae69c125…2379

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe80d5064…a5aa

0x065c9d…c394

5 touches
3 conflicts

0x07ea052e…d7e8

0x065c9d…c394

5 touches
3 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: 0xab35264b…1cfa38

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity