Block #73,223,844

← previous blocknext block →recent activity

Analyzing

Block #73,223,844

8 transactions · 8 stateful · 2026-05-08 10:34:02 UTC

Parallelism

75/100

Blocked

25%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,223,844  ·  8 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

0x388e001a…7e04

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5aeaf08b…cbf7

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x5eb2126e…31eb

0x065c9d…c394

2 touches
0 conflicts

0xc43e0178…569e

0x065c9d…c394

2 touches
0 conflicts

0xe0e0c170…2eb2

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: 0x34b6552d…112a6f

1 conflict on slot 0x388e001a16…e57e04

← previous block·next block →recent activity