Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3512a783f2783bdcc254708017f42723f6a52c502acd9752bfc262659ed74f7f

Tx prefix hash: 39b9a6f49cbde78659a7f0b20f26738b88588e909b7eea1d8a3027177dd6868e
Tx public key: d4ff41917722b6a57b5ac8be7bf59fe783f8fd07b609b21280414c7b734d846b
Timestamp: 1708252634 Timestamp [UCT]: 2024-02-18 10:37:14 Age [y:d:h:m:s]: 00:353:12:03:36
Block: 960165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252768 RingCT/type: yes/0
Extra: 01d4ff41917722b6a57b5ac8be7bf59fe783f8fd07b609b21280414c7b734d846b0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8783928b295ef061bea727ca80b6cfc529ff5f6ca09fb481feabdb80ce465b6 0.600000000000 1419726 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": 960175, "vin": [ { "gen": { "height": 960165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8783928b295ef061bea727ca80b6cfc529ff5f6ca09fb481feabdb80ce465b6" } } ], "extra": [ 1, 212, 255, 65, 145, 119, 34, 182, 165, 123, 90, 200, 190, 123, 245, 159, 231, 131, 248, 253, 7, 182, 9, 178, 18, 128, 65, 76, 123, 115, 77, 132, 107, 2, 17, 0, 0, 0, 5, 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