Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc01a955aae1ce46a417c80f3b4f8f62471004188040df735483164285abfc0c

Tx prefix hash: bb6eaa4c00f07f6af511cfaa9438149b248978afef487919f42a2ccff5dee902
Tx public key: 33d6403b260f13bb0910d4db17ddf4a945590a34b81888e05444fbae6f600d4f
Timestamp: 1576424914 Timestamp [UCT]: 2019-12-15 15:48:34 Age [y:d:h:m:s]: 05:162:12:05:17
Block: 27518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1262839 RingCT/type: yes/0
Extra: 0133d6403b260f13bb0910d4db17ddf4a945590a34b81888e05444fbae6f600d4f02110000000a9159db1e000000000000000000

1 output(s) for total of 497.533477785000 dcy

stealth address amount amount idx
00: 7da157151801bfefebdc5a47b134ae9f1c33071e2c6be3d97321e91e1a3ef9e3 497.533477785000 45524 of 0

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": 27528, "vin": [ { "gen": { "height": 27518 } } ], "vout": [ { "amount": 497533477785, "target": { "key": "7da157151801bfefebdc5a47b134ae9f1c33071e2c6be3d97321e91e1a3ef9e3" } } ], "extra": [ 1, 51, 214, 64, 59, 38, 15, 19, 187, 9, 16, 212, 219, 23, 221, 244, 169, 69, 89, 10, 52, 184, 24, 136, 224, 84, 68, 251, 174, 111, 96, 13, 79, 2, 17, 0, 0, 0, 10, 145, 89, 219, 30, 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