Block #73,273,699

← previous blocknext block →recent activity

Analyzing

Block #73,273,699

19 transactions · 18 stateful · 2026-05-08 16:05:35 UTC

Parallelism

68/100

Blocked

39%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,273,699  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…0002

0xab3526…fa38

12 touches
15 conflicts

0x47c1a8e8…f74a

0x34b655…2a6f

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x0f41c833…9c38

0x34b655…2a6f

2 touches
0 conflicts

0x693d979a…f2bd

0x34b655…2a6f

2 touches
0 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

2 touches
0 conflicts

0xcc68c0fa…d631

0x34b655…2a6f

2 touches
0 conflicts

0xea02471d…1542

0x34b655…2a6f

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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity