Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 607da92ebcbb6c5be223276efd0be5cde8c4292cd741b3f7d63ea53df20d1c76

Tx prefix hash: 485ca4c67e59d4934b9a7cc7ac9f7d1de972da09f1273665bd2eb65c03ef065c
Tx public key: 6005ea6748d6d30ecc96d522ded8325160dbc2998cbb041fd65ff7598b310665
Timestamp: 1764530077 Timestamp [UCT]: 2025-11-30 19:14:37 Age [y:d:h:m:s]: 00:022:17:35:20
Block: 1423607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16260 RingCT/type: yes/0
Extra: 016005ea6748d6d30ecc96d522ded8325160dbc2998cbb041fd65ff7598b310665021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e13f13112aa0ef75256f09b275dd14fb2bd7e0b28503dc91e4b8408648a7bdc 0.600000000000 1912224 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": 1423617, "vin": [ { "gen": { "height": 1423607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e13f13112aa0ef75256f09b275dd14fb2bd7e0b28503dc91e4b8408648a7bdc" } } ], "extra": [ 1, 96, 5, 234, 103, 72, 214, 211, 14, 204, 150, 213, 34, 222, 216, 50, 81, 96, 219, 194, 153, 140, 187, 4, 31, 214, 95, 247, 89, 139, 49, 6, 101, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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