Block #73,297,505

← previous blocknext block →recent activity

Analyzing

Block #73,297,505

19 transactions · 17 stateful · 2026-05-08 18:43:58 UTC

Parallelism

63/100

Blocked

35%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,297,505  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x0bb5dbb8…2bda

0x065c9d…c394

3 touches
1 conflict

0xde83cdd4…40ce

0x065c9d…c394

3 touches
1 conflict

0xee69d259…5be0

0x065c9d…c394

3 touches
1 conflict

0xad4badb7…f97b

0x065c9d…c394

3 touches
1 conflict

0xbdc141a2…e6fe

0x065c9d…c394

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

21 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity