Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faaaa5cf1c5182e5fcb60ce7dd4e9b7808be0316f35246e3ab5dd460e4055999

Tx prefix hash: 1adcc799f6e47a33cf9e7d56358e665a9782036a72e929b87677be8ea863cb5d
Tx public key: d81c2a438f1f3bf31c593a470e1022961c352ec7d51cbf463dafdc279d95f59d
Timestamp: 1720179248 Timestamp [UCT]: 2024-07-05 11:34:08 Age [y:d:h:m:s]: 00:272:14:23:35
Block: 1059034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194766 RingCT/type: yes/0
Extra: 01d81c2a438f1f3bf31c593a470e1022961c352ec7d51cbf463dafdc279d95f59d0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0964974d9efebd39a91ad750867e1706d0ce3fd8ef3824e82b0feae5556b2045 0.600000000000 1529493 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": 1059044, "vin": [ { "gen": { "height": 1059034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0964974d9efebd39a91ad750867e1706d0ce3fd8ef3824e82b0feae5556b2045" } } ], "extra": [ 1, 216, 28, 42, 67, 143, 31, 59, 243, 28, 89, 58, 71, 14, 16, 34, 150, 28, 53, 46, 199, 213, 28, 191, 70, 61, 175, 220, 39, 157, 149, 245, 157, 2, 17, 0, 0, 0, 5, 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