Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 688ec5f15dc9f56cc22ab8651b9ff7f22f83c496bde099ebe11072ee6c54b093

Tx prefix hash: e6490d9c3b9fda0e10eac1e30d3e6c78bbdaf7fa43c4eddbb454f3bd93803569
Tx public key: c388995b3145597e7450936f01679421fdd6a762a90abacfdccfa21f63745a5d
Timestamp: 1579094271 Timestamp [UCT]: 2020-01-15 13:17:51 Age [y:d:h:m:s]: 04:308:09:22:50
Block: 46078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109907 RingCT/type: yes/0
Extra: 01c388995b3145597e7450936f01679421fdd6a762a90abacfdccfa21f63745a5d02110000001bdcee4b4d000000000000000000

1 output(s) for total of 431.842415904000 dcy

stealth address amount amount idx
00: f8bd74c5ab80b8c0d9316dc85fa5a7fd9362ea7271c721a95211955c7b7d660c 431.842415904000 84571 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": 46088, "vin": [ { "gen": { "height": 46078 } } ], "vout": [ { "amount": 431842415904, "target": { "key": "f8bd74c5ab80b8c0d9316dc85fa5a7fd9362ea7271c721a95211955c7b7d660c" } } ], "extra": [ 1, 195, 136, 153, 91, 49, 69, 89, 126, 116, 80, 147, 111, 1, 103, 148, 33, 253, 214, 167, 98, 169, 10, 186, 207, 220, 207, 162, 31, 99, 116, 90, 93, 2, 17, 0, 0, 0, 27, 220, 238, 75, 77, 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