Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68c965b17d4579e5e40b3c078dae772195836dfb9558c2a4e91d15bc77f0e432

Tx prefix hash: 08b6a3f7966f6e5b33e24ced563025fb51c56584e27ea177520136d4d2c9af46
Tx public key: 62729757f2cb0fbec6e762164b4b90a28eb3284a703851f77e91d4992d470484
Timestamp: 1717568501 Timestamp [UCT]: 2024-06-05 06:21:41 Age [y:d:h:m:s]: 00:308:11:47:46
Block: 1037401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220466 RingCT/type: yes/0
Extra: 0162729757f2cb0fbec6e762164b4b90a28eb3284a703851f77e91d4992d4704840211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ff3bbdac9bae8d989cbf7193bf3a18254af83b48e6b7c5797abd2ba342ecad7 0.600000000000 1505932 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": 1037411, "vin": [ { "gen": { "height": 1037401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ff3bbdac9bae8d989cbf7193bf3a18254af83b48e6b7c5797abd2ba342ecad7" } } ], "extra": [ 1, 98, 114, 151, 87, 242, 203, 15, 190, 198, 231, 98, 22, 75, 75, 144, 162, 142, 179, 40, 74, 112, 56, 81, 247, 126, 145, 212, 153, 45, 71, 4, 132, 2, 17, 0, 0, 0, 1, 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