Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b50a39ab2ae7eda0c9c796be917342f0bcd52c12b55e2e420a1c50b60cfcd017

Tx prefix hash: 1491dbddc03fff369818ff4600bf7e3dacfc3da84a3d292feadf7f89ad2cfb11
Tx public key: 4399a187187231554ce3db4cef689280d31b41672c2c874c8ab4faede427ba1a
Timestamp: 1710719749 Timestamp [UCT]: 2024-03-17 23:55:49 Age [y:d:h:m:s]: 01:068:12:19:19
Block: 980632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309979 RingCT/type: yes/0
Extra: 014399a187187231554ce3db4cef689280d31b41672c2c874c8ab4faede427ba1a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3def219eaa06af0a6041e44a5d3919aee3ea2cf4ad51fa9b621cd1fd3cb21f20 0.600000000000 1440713 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": 980642, "vin": [ { "gen": { "height": 980632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3def219eaa06af0a6041e44a5d3919aee3ea2cf4ad51fa9b621cd1fd3cb21f20" } } ], "extra": [ 1, 67, 153, 161, 135, 24, 114, 49, 85, 76, 227, 219, 76, 239, 104, 146, 128, 211, 27, 65, 103, 44, 44, 135, 76, 138, 180, 250, 237, 228, 39, 186, 26, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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