Block #73,653,321

← previous blocknext block →recent activity

Analyzing

Block #73,653,321

16 transactions · 11 stateful · 2026-05-10 10:13:30 UTC

Parallelism

69/100

Blocked

36%

Avg conflicts / tx

0.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,653,321  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x217740fb…853e

0x065c9d…c394

4 touches
1 conflict

0x38fd06e6…eb3d

0x065c9d…c394

3 touches
1 conflict

0xdca46ff7…b9d5

0x065c9d…c394

3 touches
1 conflict

0xabcd7b68…042a

0x065c9d…c394

3 touches
1 conflict

0xcce2fd99…a8eb

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

3 conflicts on slot 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity