Block #73,270,681

← previous blocknext block →recent activity

Analyzing

Block #73,270,681

13 transactions · 11 stateful · 2026-05-08 15:45:30 UTC

Parallelism

77/100

Blocked

18%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,270,681  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x76156648…6b6c

0x065c9d…c394

2 touches
0 conflicts

0x7a50424c…dbc2

0x065c9d…c394

2 touches
0 conflicts

0xc199dc81…783c

0x065c9d…c394

2 touches
0 conflicts

0xc1dc7982…b7c7

0x065c9d…c394

2 touches
0 conflicts

0xd856ae3f…66d3

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity