Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eda8d4eaef85921f2ad296f2a17015319afbbcdbe9df8a33b62a70d3f74f2986

Tx prefix hash: 091f197e0cf069e539424f5ec9d08a202a9d9ba90a9d975f51bd852a1bd5ec3f
Tx public key: 511be6e394077ebcf88342c321fb8cf885b79a8a4de569b7db24e86d37f4004e
Timestamp: 1722744656 Timestamp [UCT]: 2024-08-04 04:10:56 Age [y:d:h:m:s]: 00:267:05:35:15
Block: 1080313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190903 RingCT/type: yes/0
Extra: 01511be6e394077ebcf88342c321fb8cf885b79a8a4de569b7db24e86d37f4004e02110000001a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 100d6e071d8995ed4ffe5bb4565097bce569f1cc7d4986115e3b86284c0ec289 0.600000000000 1553612 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": 1080323, "vin": [ { "gen": { "height": 1080313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "100d6e071d8995ed4ffe5bb4565097bce569f1cc7d4986115e3b86284c0ec289" } } ], "extra": [ 1, 81, 27, 230, 227, 148, 7, 126, 188, 248, 131, 66, 195, 33, 251, 140, 248, 133, 183, 154, 138, 77, 229, 105, 183, 219, 36, 232, 109, 55, 244, 0, 78, 2, 17, 0, 0, 0, 26, 145, 225, 60, 4, 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