Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: dd28e9ca0d92944f3f141d952d99f36e002d25e19c82b8326209f75ecda3fa7d

Tx prefix hash: ecbd665b5c05941d1afe2b967976852904d5abb2b7a73eaa5ea5e91c171d72a8
Tx public key: 1f16fb92c036235117169cea095309333a23e625fc75d1711d7b607661d769e1
Timestamp: 1708572540 Timestamp [UCT]: 2024-02-22 03:29:00 Age [y:d:h:m:s]: 01:030:07:24:18
Block: 962815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282694 RingCT/type: yes/0
Extra: 011f16fb92c036235117169cea095309333a23e625fc75d1711d7b607661d769e10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d8a16f8b79d26d5ef2d650ef08f31b752a971e099cb3d41caaa67f521de76c0 0.600000000000 1422500 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 962825, "vin": [ { "gen": { "height": 962815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d8a16f8b79d26d5ef2d650ef08f31b752a971e099cb3d41caaa67f521de76c0" } } ], "extra": [ 1, 31, 22, 251, 146, 192, 54, 35, 81, 23, 22, 156, 234, 9, 83, 9, 51, 58, 35, 230, 37, 252, 117, 209, 113, 29, 123, 96, 118, 97, 215, 105, 225, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8