Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da2f0f63e9cd73a761533522fea3b54104f23331ad9b1409a1cfa3cc695923bb

Tx prefix hash: 5f1e10502795e9bf51182e5e352d64c73668a10dd7300b39a4b9ce19f86010bf
Tx public key: 1f0fea47b1bb48e5926f5e9f469d66116e6a04b1c5cf6161b2a041a823f253a0
Timestamp: 1657140585 Timestamp [UCT]: 2022-07-06 20:49:45 Age [y:d:h:m:s]: 02:179:10:30:00
Block: 538113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649602 RingCT/type: yes/0
Extra: 011f0fea47b1bb48e5926f5e9f469d66116e6a04b1c5cf6161b2a041a823f253a002110000000533af99f4000000000000000000

1 output(s) for total of 10.115990186000 dcy

stealth address amount amount idx
00: cd0df333e923fdee678fef2cfd0db6d84b6abf7242ec865dfdca9ddbf1f8da9a 10.115990186000 968072 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": 538123, "vin": [ { "gen": { "height": 538113 } } ], "vout": [ { "amount": 10115990186, "target": { "key": "cd0df333e923fdee678fef2cfd0db6d84b6abf7242ec865dfdca9ddbf1f8da9a" } } ], "extra": [ 1, 31, 15, 234, 71, 177, 187, 72, 229, 146, 111, 94, 159, 70, 157, 102, 17, 110, 106, 4, 177, 197, 207, 97, 97, 178, 160, 65, 168, 35, 242, 83, 160, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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