Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e06cfc405a41ca6ed7e625fca5c97d57ce52a27a21e29940d3b0717697268f0

Tx prefix hash: e35e450bd611700a092aba28b63ecc3fe4eacdb482caaeed4ae361cac6485377
Tx public key: fb2fe50f52c4e8d8c85b876746b56fdf8521011c998f01bf190105c2ba9c93a8
Timestamp: 1636925943 Timestamp [UCT]: 2021-11-14 21:39:03 Age [y:d:h:m:s]: 03:044:16:57:18
Block: 374377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 810684 RingCT/type: yes/0
Extra: 01fb2fe50f52c4e8d8c85b876746b56fdf8521011c998f01bf190105c2ba9c93a8021100000002379224c2000000000000000000

1 output(s) for total of 35.280438602000 dcy

stealth address amount amount idx
00: 1acdb79a043cfe7da70e3813b7a39e3f401f08a984268485bf4bd338465ce474 35.280438602000 757815 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": 374387, "vin": [ { "gen": { "height": 374377 } } ], "vout": [ { "amount": 35280438602, "target": { "key": "1acdb79a043cfe7da70e3813b7a39e3f401f08a984268485bf4bd338465ce474" } } ], "extra": [ 1, 251, 47, 229, 15, 82, 196, 232, 216, 200, 91, 135, 103, 70, 181, 111, 223, 133, 33, 1, 28, 153, 143, 1, 191, 25, 1, 5, 194, 186, 156, 147, 168, 2, 17, 0, 0, 0, 2, 55, 146, 36, 194, 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