Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47f0d895b8c5df1fb062cdf15866a95534748ae4aa181ae802b3872bcbf34678

Tx prefix hash: d622d75e6d7a6610e422a6991208e1402cb11712f05cc80ad3c0e76280561260
Tx public key: bf5ff8c7e9ff54feb1fd89cde0bd982ad6853a7853ca5da7ff144e34da47f95d
Timestamp: 1721952866 Timestamp [UCT]: 2024-07-26 00:14:26 Age [y:d:h:m:s]: 00:250:10:10:04
Block: 1073739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178891 RingCT/type: yes/0
Extra: 01bf5ff8c7e9ff54feb1fd89cde0bd982ad6853a7853ca5da7ff144e34da47f95d021100000013e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f7da2794fba02693f8e4d26a5ca08263ca06d55bcb4d484e426feef20fccfde 0.600000000000 1546246 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": 1073749, "vin": [ { "gen": { "height": 1073739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f7da2794fba02693f8e4d26a5ca08263ca06d55bcb4d484e426feef20fccfde" } } ], "extra": [ 1, 191, 95, 248, 199, 233, 255, 84, 254, 177, 253, 137, 205, 224, 189, 152, 42, 214, 133, 58, 120, 83, 202, 93, 167, 255, 20, 78, 52, 218, 71, 249, 93, 2, 17, 0, 0, 0, 19, 233, 20, 221, 21, 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