Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95a148077b210868caa39581511d8b6a9b07df7b39944dac02ef6623be4474e0

Tx prefix hash: 65314d4ddc9fa737fc5d7974bbac3a530e025a44a8f10ced1d99d56ae4a9fae1
Tx public key: f8266535878e647f4f7dad5605ecb7a64345cd1c40f2e943e6dcb3fb1718ebc6
Timestamp: 1709488222 Timestamp [UCT]: 2024-03-03 17:50:22 Age [y:d:h:m:s]: 01:078:16:10:11
Block: 970416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317263 RingCT/type: yes/0
Extra: 01f8266535878e647f4f7dad5605ecb7a64345cd1c40f2e943e6dcb3fb1718ebc60211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efcc3cc1f841a722abf206da0aa3a7551d722cd4905bf4f498a3ee90400345a2 0.600000000000 1430269 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": 970426, "vin": [ { "gen": { "height": 970416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efcc3cc1f841a722abf206da0aa3a7551d722cd4905bf4f498a3ee90400345a2" } } ], "extra": [ 1, 248, 38, 101, 53, 135, 142, 100, 127, 79, 125, 173, 86, 5, 236, 183, 166, 67, 69, 205, 28, 64, 242, 233, 67, 230, 220, 179, 251, 23, 24, 235, 198, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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