Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20ec1fb9fcf96507f5a733d46476835c3da8b03c6cdb1e374019a37008911c48

Tx prefix hash: 2ba23861d49923c9bab1a0f731856be58bcee1e700417a4b7c79971cd34ab90c
Tx public key: 8c2f4e51f44e9487cb5ec54a1e22b7477fefe03497a127a69a779220f548f649
Timestamp: 1708280111 Timestamp [UCT]: 2024-02-18 18:15:11 Age [y:d:h:m:s]: 01:114:02:32:58
Block: 960392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342606 RingCT/type: yes/0
Extra: 018c2f4e51f44e9487cb5ec54a1e22b7477fefe03497a127a69a779220f548f6490211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb4b941dfeb5d56149bcd38de2edbaa5607dd04b178a0e36b8a29df10b94e66e 0.600000000000 1419955 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": 960402, "vin": [ { "gen": { "height": 960392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb4b941dfeb5d56149bcd38de2edbaa5607dd04b178a0e36b8a29df10b94e66e" } } ], "extra": [ 1, 140, 47, 78, 81, 244, 78, 148, 135, 203, 94, 197, 74, 30, 34, 183, 71, 127, 239, 224, 52, 151, 161, 39, 166, 154, 119, 146, 32, 245, 72, 246, 73, 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