Block #73,504,973

← previous blocknext block →recent activity

Analyzing

Block #73,504,973

20 transactions · 17 stateful · 2026-05-09 17:44:35 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,504,973  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xb81d3ee7…3947

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x2a1e963e…2c91

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

6 conflicts on slot 0x4d87512b00…43897c

← previous block·next block →recent activity