Block #73,384,040

← previous blocknext block →recent activity

Analyzing

Block #73,384,040

15 transactions · 10 stateful · 2026-05-09 04:19:38 UTC

Parallelism

87/100

Blocked

10%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,384,040  ·  15 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x24cfe713…0f91

0x25d593…7777

2 touches
0 conflicts

0x00000000…000b

0x2a347b…e9d3

2 touches
0 conflicts

0x8e07e07d…65ff

0x30611e…d8d9

2 touches
0 conflicts

0x8e07e07d…6600

0x30611e…d8d9

2 touches
0 conflicts

0xac2a0273…7212

0x34b655…2a6f

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity