Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 149a0a79aa7e490a84c5db8ee27e3560e5cfc0c2eb0179334af658b75150e38c

Tx prefix hash: edf42736840202629503c6e4b27ee522c5a3d437d530983ed76ede1858b3ffd2
Tx public key: 5a66d5361b9e0a350bae72aa12a3b6f1fde166b6b18b044fc03aa45fe7c7338e
Timestamp: 1625415099 Timestamp [UCT]: 2021-07-04 16:11:39 Age [y:d:h:m:s]: 04:124:20:55:41
Block: 288230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117274 RingCT/type: yes/0
Extra: 015a66d5361b9e0a350bae72aa12a3b6f1fde166b6b18b044fc03aa45fe7c7338e0211000000010f4c30de000000000000000000

1 output(s) for total of 68.075356406000 dcy

stealth address amount amount idx
00: fcd1d07a079dcdb3c2cdf3e68350b924387693e0f3fb5fb7b6422194a3c1e59f 68.075356406000 603915 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": 288240, "vin": [ { "gen": { "height": 288230 } } ], "vout": [ { "amount": 68075356406, "target": { "key": "fcd1d07a079dcdb3c2cdf3e68350b924387693e0f3fb5fb7b6422194a3c1e59f" } } ], "extra": [ 1, 90, 102, 213, 54, 27, 158, 10, 53, 11, 174, 114, 170, 18, 163, 182, 241, 253, 225, 102, 182, 177, 139, 4, 79, 192, 58, 164, 95, 231, 199, 51, 142, 2, 17, 0, 0, 0, 1, 15, 76, 48, 222, 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