Block #73,360,513

← previous blocknext block →recent activity

Analyzing

Block #73,360,513

12 transactions · 11 stateful · 2026-05-09 01:43:05 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,360,513  ·  12 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

0x7ffb7084…d97b

0x065c9d…c394

4 touches
1 conflict

0x659c24cc…ebf8

0x065c9d…c394

3 touches
1 conflict

0x6768a700…2fbc

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x06fc6d24…bb9e

0x065c9d…c394

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

2 touches
0 conflicts

0x0fc41e7b…6831

0x98dc6e…8633

2 touches
0 conflicts

0x5b571ba0…f13a

0x98dc6e…8633

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 0x7ffb7084e0…8ad97b

← previous block·next block →recent activity