Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ea3d2121daaf168b53eb1a8dd3342915dc17d1c059df7c1620cd32ceb1b3499

Tx prefix hash: d2b6a6a83297421d9b7d8808a295be43f5524f023e7c48afdcfcf6a5fe2a2c62
Tx public key: 2f7f02f573a93c2290fb3df899e80ac00767584d12a91fbe1c5d1482138d1e14
Timestamp: 1676977010 Timestamp [UCT]: 2023-02-21 10:56:50 Age [y:d:h:m:s]: 02:041:12:30:44
Block: 701755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551253 RingCT/type: yes/0
Extra: 012f7f02f573a93c2290fb3df899e80ac00767584d12a91fbe1c5d1482138d1e1402110000000874b6d784000000000000000000

1 output(s) for total of 2.902647402000 dcy

stealth address amount amount idx
00: de4d41222ae9a98fdfa20982fdfd4465133b9c00fda8372aebcf81dc5c8b6d05 2.902647402000 1145246 of 0

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": 701765, "vin": [ { "gen": { "height": 701755 } } ], "vout": [ { "amount": 2902647402, "target": { "key": "de4d41222ae9a98fdfa20982fdfd4465133b9c00fda8372aebcf81dc5c8b6d05" } } ], "extra": [ 1, 47, 127, 2, 245, 115, 169, 60, 34, 144, 251, 61, 248, 153, 232, 10, 192, 7, 103, 88, 77, 18, 169, 31, 190, 28, 93, 20, 130, 19, 141, 30, 20, 2, 17, 0, 0, 0, 8, 116, 182, 215, 132, 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