Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2552326c779853d0a21daf50d7d9fea5ce8b106627a571385ece01e66077d458

Tx prefix hash: bafa033b17fd291398431a0a3648c328fc38d66d0ea2613e37150dd8ce2a32c9
Tx public key: 81c3bdfd542a3f541c3e503b95b72da568513856abe7c1b2d3d223379a629dde
Timestamp: 1713270616 Timestamp [UCT]: 2024-04-16 12:30:16 Age [y:d:h:m:s]: 01:047:14:22:25
Block: 1001746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295026 RingCT/type: yes/0
Extra: 0181c3bdfd542a3f541c3e503b95b72da568513856abe7c1b2d3d223379a629dde0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 478ece5f5e7d01e97624446ebadc9e45f60c0c4e949d88746b96d7907c62ff60 0.600000000000 1462258 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": 1001756, "vin": [ { "gen": { "height": 1001746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "478ece5f5e7d01e97624446ebadc9e45f60c0c4e949d88746b96d7907c62ff60" } } ], "extra": [ 1, 129, 195, 189, 253, 84, 42, 63, 84, 28, 62, 80, 59, 149, 183, 45, 165, 104, 81, 56, 86, 171, 231, 193, 178, 211, 210, 35, 55, 154, 98, 157, 222, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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