Block #73,393,693

← previous blocknext block →recent activity

Analyzing

Block #73,393,693

10 transactions · 8 stateful · 2026-05-09 05:23:54 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.3

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,393,693  ·  10 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

0x4708fdde…3514

0x065c9d…c394

4 touches
1 conflict

0x90c4d6d2…0785

0x065c9d…c394

3 touches
1 conflict

0x8689a825…f544

0x065c9d…c394

3 touches
1 conflict

0x2e08a4c9…c47e

0x065c9d…c394

2 touches
0 conflicts

0x04183f8d…069e

0x34b655…2a6f

2 touches
0 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 conflicts

0x1bc9b1ca…85ef

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