Block #73,571,580

← previous blocknext block →recent activity

Analyzing

Block #73,571,580

11 transactions · 10 stateful · 2026-05-10 01:06:58 UTC

Parallelism

55/100

Blocked

50%

Avg conflicts / tx

1.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,571,580  ·  11 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x1e4d5577…29e4

0x065c9d…c394

2 touches
0 conflicts

0x210fa626…1744

0x065c9d…c394

2 touches
0 conflicts

0x83e3c003…1c74

0x065c9d…c394

2 touches
0 conflicts

0xe35b171a…b47b

0x065c9d…c394

2 touches
0 conflicts

0xff141982…0d4c

0x065c9d…c394

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity