Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdd85ad48a216ed79bbad27b2f231b4b8fa19dedc402b72d7925c8f0a14ff30a

Tx prefix hash: 18de20fadfdeead218ff53159d60220b741942cb9ca6b2e7b5a1b62282113b24
Tx public key: 2b45c4d3e626b0fc799db80e8e3481134a1a6f5eb8109b8ce871c0741778efbf
Timestamp: 1710748713 Timestamp [UCT]: 2024-03-18 07:58:33 Age [y:d:h:m:s]: 01:262:05:32:47
Block: 980883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446131 RingCT/type: yes/0
Extra: 012b45c4d3e626b0fc799db80e8e3481134a1a6f5eb8109b8ce871c0741778efbf0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 335e7797cd052e33623b39f663483aababe8d6ede7bb964852abfb18eecfea4d 0.600000000000 1440968 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": 980893, "vin": [ { "gen": { "height": 980883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "335e7797cd052e33623b39f663483aababe8d6ede7bb964852abfb18eecfea4d" } } ], "extra": [ 1, 43, 69, 196, 211, 230, 38, 176, 252, 121, 157, 184, 14, 142, 52, 129, 19, 74, 26, 111, 94, 184, 16, 155, 140, 232, 113, 192, 116, 23, 120, 239, 191, 2, 17, 0, 0, 0, 3, 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