Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78583ab95e157c04c8572331daaf6e77447f294a27e1a13a9a9fa4c807d1f322

Tx prefix hash: 4bb8c0f68b788e941f2fef9e8290827fa8e9c102f4f306050e6cd21495f0832f
Tx public key: e85a5a26ed82fecf4e6e8bb3fe6ddeaf32bf4c2c9dc20129bab58854db522bb3
Timestamp: 1713404279 Timestamp [UCT]: 2024-04-18 01:37:59 Age [y:d:h:m:s]: 00:313:23:01:22
Block: 1002857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224436 RingCT/type: yes/0
Extra: 01e85a5a26ed82fecf4e6e8bb3fe6ddeaf32bf4c2c9dc20129bab58854db522bb302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19e056c445ec5cbe444a794013e5cc147b8e11e20e8f104add0544d34dab1930 0.600000000000 1463385 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": 1002867, "vin": [ { "gen": { "height": 1002857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19e056c445ec5cbe444a794013e5cc147b8e11e20e8f104add0544d34dab1930" } } ], "extra": [ 1, 232, 90, 90, 38, 237, 130, 254, 207, 78, 110, 139, 179, 254, 109, 222, 175, 50, 191, 76, 44, 157, 194, 1, 41, 186, 181, 136, 84, 219, 82, 43, 179, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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