Block #73,641,521

← previous blocknext block →recent activity

Analyzing

Block #73,641,521

17 transactions · 14 stateful · 2026-05-10 08:54:01 UTC

Parallelism

53/100

Blocked

64%

Avg conflicts / tx

1.76

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,641,521  ·  17 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

0x00000000…003d

0x065c9d…c394

16 touches
28 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xf9fe3c67…7bac

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x966e446b…0ace

0xd32edf…ff58

3 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: 0x065c9d28…a9c394

28 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity