Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 578edaf7fc2ab91f8459771a25dec52346ac06a6889b79daf35adb4a54ce59e9

Tx prefix hash: a0c590f903d9e306d90e3b051d1d18fd9e012f67f67afefd13cc12888c04dbf4
Tx public key: 04641e19c6574b17c433710fe7f6d582786b0f99be70e7ed78bd10323473b69f
Timestamp: 1713597504 Timestamp [UCT]: 2024-04-20 07:18:24 Age [y:d:h:m:s]: 01:032:03:53:06
Block: 1004453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283980 RingCT/type: yes/0
Extra: 0104641e19c6574b17c433710fe7f6d582786b0f99be70e7ed78bd10323473b69f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 714d62efa57a9b6c799f08cc7c14aaafdc92a3e9e98d3d953369824fa5e1d567 0.600000000000 1465021 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": 1004463, "vin": [ { "gen": { "height": 1004453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "714d62efa57a9b6c799f08cc7c14aaafdc92a3e9e98d3d953369824fa5e1d567" } } ], "extra": [ 1, 4, 100, 30, 25, 198, 87, 75, 23, 196, 51, 113, 15, 231, 246, 213, 130, 120, 107, 15, 153, 190, 112, 231, 237, 120, 189, 16, 50, 52, 115, 182, 159, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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