Block #73,200,436

← previous blocknext block →recent activity

Analyzing

Block #73,200,436

10 transactions · 8 stateful · 2026-05-08 07:58:16 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,200,436  ·  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

0x8e66da19…66b6

0x065c9d…c394

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0xade7be6a…9db8

0x065c9d…c394

2 touches
0 conflicts

0x438cf5f6…f077

0x2a68ba…90c5

2 touches
0 conflicts

0x70b2f813…783c

0x2a68ba…90c5

2 touches
0 conflicts

0x247cfb80…cca8

0x34b655…2a6f

2 touches
0 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

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 0x8e66da1932…c966b6

← previous block·next block →recent activity