Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ac5c54af5dcba8b2cf5055e26cdcf3baa646fa42e0502ef6af1f66b37d3b1cd

Tx prefix hash: 03dc5fed16b68059cb5b19ed9545300d1be8611cfd3898e3f78216fcaa31e81e
Tx public key: 1ff4ab42210bd3927c8812bc03e839b96c8ae2e4e27883bda320c1383e124d87
Timestamp: 1696920163 Timestamp [UCT]: 2023-10-10 06:42:43 Age [y:d:h:m:s]: 01:091:04:39:47
Block: 866420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326426 RingCT/type: yes/0
Extra: 011ff4ab42210bd3927c8812bc03e839b96c8ae2e4e27883bda320c1383e124d870211000000024b8f5122000000000000000000

1 output(s) for total of 0.826401134000 dcy

stealth address amount amount idx
00: 4e00aff716df59d24bca86a956bd57d52fea0a0a535f9d148dbedd947ea03c81 0.826401134000 1321012 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": 866430, "vin": [ { "gen": { "height": 866420 } } ], "vout": [ { "amount": 826401134, "target": { "key": "4e00aff716df59d24bca86a956bd57d52fea0a0a535f9d148dbedd947ea03c81" } } ], "extra": [ 1, 31, 244, 171, 66, 33, 11, 211, 146, 124, 136, 18, 188, 3, 232, 57, 185, 108, 138, 226, 228, 226, 120, 131, 189, 163, 32, 193, 56, 62, 18, 77, 135, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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