Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a17c62deb0d11b9c5673975f3fd7ad17310d5cc7e689119d766b108684862a24

Tx prefix hash: 6d57244cbcd53cc94710a016facfd802a2f320babad5f254f8e213094cbab641
Tx public key: 4b5274a7638ea76b983376e4e8f4d632c34c349bfe3c3591da532362264caf40
Timestamp: 1708841792 Timestamp [UCT]: 2024-02-25 06:16:32 Age [y:d:h:m:s]: 01:053:23:52:46
Block: 965058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299599 RingCT/type: yes/0
Extra: 014b5274a7638ea76b983376e4e8f4d632c34c349bfe3c3591da532362264caf400211000000147a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e670a9f34a7b00a2543fd6b6f5a4b06013a21e5afcd413de064cc5a2f59dc801 0.600000000000 1424805 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": 965068, "vin": [ { "gen": { "height": 965058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e670a9f34a7b00a2543fd6b6f5a4b06013a21e5afcd413de064cc5a2f59dc801" } } ], "extra": [ 1, 75, 82, 116, 167, 99, 142, 167, 107, 152, 51, 118, 228, 232, 244, 214, 50, 195, 76, 52, 155, 254, 60, 53, 145, 218, 83, 35, 98, 38, 76, 175, 64, 2, 17, 0, 0, 0, 20, 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