Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e112efb6a154b81fdbb366876edc5c4237740081f40559afad55a4262721f702

Tx prefix hash: 5f9c0629f6c793a9a9bf0814db8e3aaac731a9318f8e8be829245638435c5c31
Tx public key: f7153786634bd7c28a4f3e430245d80f0c2f655dd5fdcea790d324fd0edf151c
Timestamp: 1721980909 Timestamp [UCT]: 2024-07-26 08:01:49 Age [y:d:h:m:s]: 00:181:06:29:37
Block: 1073975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129654 RingCT/type: yes/0
Extra: 01f7153786634bd7c28a4f3e430245d80f0c2f655dd5fdcea790d324fd0edf151c02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae06fd25e4e78d05425f9cc5552cdf9d7929cf9cf226e7f88cc47cea52ea19b3 0.600000000000 1546484 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": 1073985, "vin": [ { "gen": { "height": 1073975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae06fd25e4e78d05425f9cc5552cdf9d7929cf9cf226e7f88cc47cea52ea19b3" } } ], "extra": [ 1, 247, 21, 55, 134, 99, 75, 215, 194, 138, 79, 62, 67, 2, 69, 216, 15, 12, 47, 101, 93, 213, 253, 206, 167, 144, 211, 36, 253, 14, 223, 21, 28, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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