Block #73,503,155

← previous blocknext block →recent activity

Analyzing

Block #73,503,155

12 transactions · 12 stateful · 2026-05-09 17:32:27 UTC

Parallelism

67/100

Blocked

58%

Avg conflicts / tx

1.08

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,503,155  ·  12 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

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x5593214e…dfc1

0x3bd359…433a

4 touches
1 conflict

0x00000000…0001

0x75c3ab…4f0d

4 touches
1 conflict

0x4d1acd7c…f345

0x5e1b1a…7777

4 touches
1 conflict

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

6 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity