Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb50744007027c9e520d5e7184a9591f015f595e728b2facf3fe6d92c9c00afe

Tx prefix hash: 799f30950c56cbe9e7975aff023eb5e7d8bc38cd47823c93e83a3de70d96be83
Tx public key: a9b9c0673bafb55b7dfddce10079c207d4da3991e6a9dea0604597d506f91495
Timestamp: 1702149072 Timestamp [UCT]: 2023-12-09 19:11:12 Age [y:d:h:m:s]: 01:038:15:57:52
Block: 909566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288988 RingCT/type: yes/0
Extra: 01a9b9c0673bafb55b7dfddce10079c207d4da3991e6a9dea0604597d506f9149502110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e3404266f56ff1df433e638a4049ef5992fc48ea24203767681bcc2a8d86293 0.600000000000 1366665 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": 909576, "vin": [ { "gen": { "height": 909566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e3404266f56ff1df433e638a4049ef5992fc48ea24203767681bcc2a8d86293" } } ], "extra": [ 1, 169, 185, 192, 103, 59, 175, 181, 91, 125, 253, 220, 225, 0, 121, 194, 7, 212, 218, 57, 145, 230, 169, 222, 160, 96, 69, 151, 213, 6, 249, 20, 149, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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