Block #73,270,692

← previous blocknext block →recent activity

Analyzing

Block #73,270,692

11 transactions · 10 stateful · 2026-05-08 15:45:34 UTC

Parallelism

82/100

Blocked

10%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,270,692  ·  11 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

0xd6aabe89…92f5

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x17e63c13…80c1

0x065c9d…c394

2 touches
0 conflicts

0x2ba777ca…1a1d

0x065c9d…c394

2 touches
0 conflicts

0x42ad369c…794b

0x065c9d…c394

2 touches
0 conflicts

0x5b5630ef…0446

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 0xd6aabe893a…bf92f5

← previous block·next block →recent activity