Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d88cf52388bad517b4bf865cf2b6e1344f0b3aed8d7fb6f1fec17386d22b4b6f

Tx prefix hash: 0fbaee5ebc6a3d3a4e75b48b62d02000a159dc4d4cbc736a7e77024335b06991
Tx public key: f6ae77bb8bb1f7613d3a0522f65fd3675aa6ab04c88892b13d59b6fdb64c0ce3
Timestamp: 1710661547 Timestamp [UCT]: 2024-03-17 07:45:47 Age [y:d:h:m:s]: 01:024:02:44:10
Block: 980158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278195 RingCT/type: yes/0
Extra: 01f6ae77bb8bb1f7613d3a0522f65fd3675aa6ab04c88892b13d59b6fdb64c0ce30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 570e357fdfc7902549f8c40a26fa27c98009b2b4663d56e084e038bc3dc4603e 0.600000000000 1440217 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": 980168, "vin": [ { "gen": { "height": 980158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "570e357fdfc7902549f8c40a26fa27c98009b2b4663d56e084e038bc3dc4603e" } } ], "extra": [ 1, 246, 174, 119, 187, 139, 177, 247, 97, 61, 58, 5, 34, 246, 95, 211, 103, 90, 166, 171, 4, 200, 136, 146, 177, 61, 89, 182, 253, 182, 76, 12, 227, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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