Block #73,493,333

← previous blocknext block →recent activity

Analyzing

Block #73,493,333

14 transactions · 10 stateful · 2026-05-09 16:27:00 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,493,333  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xbe010524…6b24

0x065c9d…c394

3 touches
1 conflict

0x32cc2991…8f45

0x065c9d…c394

2 touches
0 conflicts

0x1b8c2514…d1a8

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 0x22e295f5d8…ac1bef

← previous block·next block →recent activity