Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71c2e6afa1bfbebca811deac8788392d5e898a64134a450f40f56f83b506191d

Tx prefix hash: d3c9f5dac803120a773d170c09c82809b9a01e40030a006780d0068f57148de2
Tx public key: 65e8c27acd17e3fb50825de20accc0d21f2853adb76298bf7b43927feb994ff1
Timestamp: 1700233190 Timestamp [UCT]: 2023-11-17 14:59:50 Age [y:d:h:m:s]: 01:355:08:14:49
Block: 893685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512840 RingCT/type: yes/0
Extra: 0165e8c27acd17e3fb50825de20accc0d21f2853adb76298bf7b43927feb994ff1021100000002faf35c9c000000000000000000

1 output(s) for total of 0.671197919000 dcy

stealth address amount amount idx
00: 89cdd9cb19e6a6ef7d6aeef7a0a483d34787efd10a16c5debadc5645f45f9f05 0.671197919000 1349868 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": 893695, "vin": [ { "gen": { "height": 893685 } } ], "vout": [ { "amount": 671197919, "target": { "key": "89cdd9cb19e6a6ef7d6aeef7a0a483d34787efd10a16c5debadc5645f45f9f05" } } ], "extra": [ 1, 101, 232, 194, 122, 205, 23, 227, 251, 80, 130, 93, 226, 10, 204, 192, 210, 31, 40, 83, 173, 183, 98, 152, 191, 123, 67, 146, 127, 235, 153, 79, 241, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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