Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9deca258ac8e7cfaecf919b22438923cc8a49c9d4a897612baf816288cd7ade

Tx prefix hash: f19bbf0ac5084ab22eee423e128cb5677177dfaa40d291b3e28bf355a31cb8ea
Tx public key: 03be4dd16953fb48703c810c1d33ce41ecb6e647f773fc818d71cbc04f564cba
Timestamp: 1708702846 Timestamp [UCT]: 2024-02-23 15:40:46 Age [y:d:h:m:s]: 01:095:10:18:26
Block: 963905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329263 RingCT/type: yes/0
Extra: 0103be4dd16953fb48703c810c1d33ce41ecb6e647f773fc818d71cbc04f564cba02110000001459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 267b7d3214ac8fc591e9e39ce52a2bb7a55ae2ae15e4a647f7e70449ff2e9549 0.600000000000 1423632 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": 963915, "vin": [ { "gen": { "height": 963905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "267b7d3214ac8fc591e9e39ce52a2bb7a55ae2ae15e4a647f7e70449ff2e9549" } } ], "extra": [ 1, 3, 190, 77, 209, 105, 83, 251, 72, 112, 60, 129, 12, 29, 51, 206, 65, 236, 182, 230, 71, 247, 115, 252, 129, 141, 113, 203, 192, 79, 86, 76, 186, 2, 17, 0, 0, 0, 20, 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