Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d35cb00d31cbcda34fc3e6be4e0de61e06931330b597cef3dd71b36064051f46

Tx prefix hash: 831038832b4fec586965cc5d79bb094c88dd4a160f5c8ea653c2d08b639d45bd
Tx public key: 42ed5a895dffcc3e1015e8f497f022442f746cb25f7e80b899f75be7aae20799
Timestamp: 1725012581 Timestamp [UCT]: 2024-08-30 10:09:41 Age [y:d:h:m:s]: 00:289:22:34:38
Block: 1099114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207004 RingCT/type: yes/0
Extra: 0142ed5a895dffcc3e1015e8f497f022442f746cb25f7e80b899f75be7aae2079902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27d5778d18664b6c76a1c0c192b3374fb1cb2f60532c7f6c45e9c8bfa06ca2d5 0.600000000000 1575041 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": 1099124, "vin": [ { "gen": { "height": 1099114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27d5778d18664b6c76a1c0c192b3374fb1cb2f60532c7f6c45e9c8bfa06ca2d5" } } ], "extra": [ 1, 66, 237, 90, 137, 93, 255, 204, 62, 16, 21, 232, 244, 151, 240, 34, 68, 47, 116, 108, 178, 95, 126, 128, 184, 153, 247, 91, 231, 170, 226, 7, 153, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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