Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdfde022123626c077984d48224fa2c407ff1f373c03bc1021d5828c1cfe6a7d

Tx prefix hash: 869d28c933b24ecfc67d8c311117511dd8bbcfb533eb24ce0b5a9b9752190eab
Tx public key: c0d0ff39eb996be5efb40580c9b2a439ab734a42edf884da060d4964cb761ce8
Timestamp: 1645547850 Timestamp [UCT]: 2022-02-22 16:37:30 Age [y:d:h:m:s]: 02:336:20:30:10
Block: 444171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 760134 RingCT/type: yes/0
Extra: 01c0d0ff39eb996be5efb40580c9b2a439ab734a42edf884da060d4964cb761ce8021100000024c9067537000000000000000000

1 output(s) for total of 20.714639526000 dcy

stealth address amount amount idx
00: 30599608f1774c527bb67fc353c0dae57e0b054e950c5870b86b6ff363908b9e 20.714639526000 857380 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": 444181, "vin": [ { "gen": { "height": 444171 } } ], "vout": [ { "amount": 20714639526, "target": { "key": "30599608f1774c527bb67fc353c0dae57e0b054e950c5870b86b6ff363908b9e" } } ], "extra": [ 1, 192, 208, 255, 57, 235, 153, 107, 229, 239, 180, 5, 128, 201, 178, 164, 57, 171, 115, 74, 66, 237, 248, 132, 218, 6, 13, 73, 100, 203, 118, 28, 232, 2, 17, 0, 0, 0, 36, 201, 6, 117, 55, 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