Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21a9a8730d79c12a2bf31aa93c389d9e7b457c28e3148090d74bb3d2dfcc5c00

Tx prefix hash: 49276b7bee6ed698a9e054307ddb3de47634c2c3494b76b8407881b5e696ddae
Tx public key: 780e48e9767543ab8068822c31b9248ad14865e1da0dbca6f6fe3f98b8a6236b
Timestamp: 1708525727 Timestamp [UCT]: 2024-02-21 14:28:47 Age [y:d:h:m:s]: 01:304:19:48:35
Block: 962425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476656 RingCT/type: yes/0
Extra: 01780e48e9767543ab8068822c31b9248ad14865e1da0dbca6f6fe3f98b8a6236b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 645c6ac3c306e7e737f57dd7193d78904851db74adffabfab058d32e15d2f65f 0.600000000000 1422060 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": 962435, "vin": [ { "gen": { "height": 962425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "645c6ac3c306e7e737f57dd7193d78904851db74adffabfab058d32e15d2f65f" } } ], "extra": [ 1, 120, 14, 72, 233, 118, 117, 67, 171, 128, 104, 130, 44, 49, 185, 36, 138, 209, 72, 101, 225, 218, 13, 188, 166, 246, 254, 63, 152, 184, 166, 35, 107, 2, 17, 0, 0, 0, 2, 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