Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c82ae98bc60758550a2f4f35030793bb8318f6537fed8dfcf83d748efbbc5b1

Tx prefix hash: ca504ef04e1b4ace6eb75f50e11c5f08515132549ee7716e6679383e7616c736
Tx public key: d1b7aef1787571d5b7b79daa954471a741cf6f383487d287ecb8dfb1935dc9ca
Timestamp: 1707276542 Timestamp [UCT]: 2024-02-07 03:29:02 Age [y:d:h:m:s]: 00:350:20:38:29
Block: 952064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251133 RingCT/type: yes/0
Extra: 01d1b7aef1787571d5b7b79daa954471a741cf6f383487d287ecb8dfb1935dc9ca0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61df35a5fc4a9a3dad3610cdca66dafe9d4959b20f14c7c438447306c323e05a 0.600000000000 1410940 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": 952074, "vin": [ { "gen": { "height": 952064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61df35a5fc4a9a3dad3610cdca66dafe9d4959b20f14c7c438447306c323e05a" } } ], "extra": [ 1, 209, 183, 174, 241, 120, 117, 113, 213, 183, 183, 157, 170, 149, 68, 113, 167, 65, 207, 111, 56, 52, 135, 210, 135, 236, 184, 223, 177, 147, 93, 201, 202, 2, 17, 0, 0, 0, 1, 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