Block #73,360,508

← previous blocknext block →recent activity

Analyzing

Block #73,360,508

15 transactions · 14 stateful · 2026-05-09 01:43:03 UTC

Parallelism

87/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,360,508  ·  15 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

2 touches
0 conflicts

0xeef891c1…6bcf

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0xd59f6ed1…03ea

0x1b6862…e19c

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity