Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c52996f6dee6e309c8d4c1c567fdc85552e8f28dd51f1a1f2c8d7df4070d1423

Tx prefix hash: cf3a87bf41cccbbcb9cb2d75113d49bfe5a4b57ec77b0d99b45c8298dca4daa4
Tx public key: 8c64ebc95f935dfda445272f15835fb6de04484ef0c3c1aad154b1f4aa729a4c
Timestamp: 1735317145 Timestamp [UCT]: 2024-12-27 16:32:25 Age [y:d:h:m:s]: 00:106:15:18:44
Block: 1184409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76011 RingCT/type: yes/0
Extra: 018c64ebc95f935dfda445272f15835fb6de04484ef0c3c1aad154b1f4aa729a4c02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69ee859666e4d1aba260cd4153da92d5a0320ef610366f5a7cc8116f5dcea261 0.600000000000 1670866 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": 1184419, "vin": [ { "gen": { "height": 1184409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69ee859666e4d1aba260cd4153da92d5a0320ef610366f5a7cc8116f5dcea261" } } ], "extra": [ 1, 140, 100, 235, 201, 95, 147, 93, 253, 164, 69, 39, 47, 21, 131, 95, 182, 222, 4, 72, 78, 240, 195, 193, 170, 209, 84, 177, 244, 170, 114, 154, 76, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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