Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a276e85b8511ef8853a857f47d9e7838431a8a761f518137a22f23761e1a199b

Tx prefix hash: c7acaef6daf0c55be6763f50090ac9ca717563caf30e2c7e59127510ff5b2c14
Tx public key: 716db5d5f5ef5f34173ef3ca8adf760322fe35d0d858e64feb9dab856b45ed1e
Timestamp: 1725743483 Timestamp [UCT]: 2024-09-07 21:11:23 Age [y:d:h:m:s]: 01:063:10:20:34
Block: 1105173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303763 RingCT/type: yes/0
Extra: 01716db5d5f5ef5f34173ef3ca8adf760322fe35d0d858e64feb9dab856b45ed1e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e5644f6b51248136f8415c46f1d03d8747265cce7c6ccdc0af2421683ab3e80 0.600000000000 1582512 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": 1105183, "vin": [ { "gen": { "height": 1105173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e5644f6b51248136f8415c46f1d03d8747265cce7c6ccdc0af2421683ab3e80" } } ], "extra": [ 1, 113, 109, 181, 213, 245, 239, 95, 52, 23, 62, 243, 202, 138, 223, 118, 3, 34, 254, 53, 208, 216, 88, 230, 79, 235, 157, 171, 133, 107, 69, 237, 30, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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