Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b17ca33c3596eba837562d87a10aa582f771c0ebec771f3e754e6014ccd99288

Tx prefix hash: 6a290509642ed4a71fc80ff07680d8c972596d24767bae22a15914697f2ba0a2
Tx public key: a971f31e898977b618f8806a82c183ad210df3cd75a1c4c18ec2fae59caa0f4f
Timestamp: 1712114836 Timestamp [UCT]: 2024-04-03 03:27:16 Age [y:d:h:m:s]: 01:012:21:07:20
Block: 992149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270197 RingCT/type: yes/0
Extra: 01a971f31e898977b618f8806a82c183ad210df3cd75a1c4c18ec2fae59caa0f4f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c42c22853b25280d04fb5cfa91d7c326d2077f38afb3bfeb1618190051d9bca 0.600000000000 1452487 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": 992159, "vin": [ { "gen": { "height": 992149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c42c22853b25280d04fb5cfa91d7c326d2077f38afb3bfeb1618190051d9bca" } } ], "extra": [ 1, 169, 113, 243, 30, 137, 137, 119, 182, 24, 248, 128, 106, 130, 193, 131, 173, 33, 13, 243, 205, 117, 161, 196, 193, 142, 194, 250, 229, 156, 170, 15, 79, 2, 17, 0, 0, 0, 3, 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