Block #73,571,575

← previous blocknext block →recent activity

Analyzing

Block #73,571,575

17 transactions · 16 stateful · 2026-05-10 01:06:56 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

1.12

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,571,575  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xb81d3ee7…3947

0x34b655…2a6f

4 touches
1 conflict

0x00000000…000b

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dba

0x6c4bfa…a540

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

10 conflicts on slot 0x4d87512b00…43897c

← previous block·next block →recent activity