Block #73,353,268

← previous blocknext block →recent activity

Analyzing

Block #73,353,268

12 transactions · 9 stateful · 2026-05-09 00:55:04 UTC

Parallelism

83/100

Blocked

22%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,353,268  ·  12 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

0xb81d3ee7…3947

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x197d59cb…de7c

0x065c9d…c394

2 touches
0 conflicts

0x341d80d6…c8a4

0x065c9d…c394

2 touches
0 conflicts

0x3e15d15d…2ebb

0x065c9d…c394

2 touches
0 conflicts

0x53342766…a4b7

0x065c9d…c394

2 touches
0 conflicts

0x8cb8b5b9…5fae

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity