Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5af85de88e4b802b587efd77b77e00f3664bc07e76903b08f9fdd7ef3ad81df

Tx prefix hash: a76e68ae17506319b1de9fc73a481465e07c69e416bbe20156d67807f45d63ee
Tx public key: 2704cfae42ad4683c5cff82a1acc624cdbc6bdc2096f503b6f5e968e235e21c5
Timestamp: 1716313016 Timestamp [UCT]: 2024-05-21 17:36:56 Age [y:d:h:m:s]: 00:342:01:55:32
Block: 1026990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244512 RingCT/type: yes/0
Extra: 012704cfae42ad4683c5cff82a1acc624cdbc6bdc2096f503b6f5e968e235e21c50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bbfeb2040711f4a3a603c094f9afe9a078f4366967232bf41c3c335ce862503 0.600000000000 1494377 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": 1027000, "vin": [ { "gen": { "height": 1026990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bbfeb2040711f4a3a603c094f9afe9a078f4366967232bf41c3c335ce862503" } } ], "extra": [ 1, 39, 4, 207, 174, 66, 173, 70, 131, 197, 207, 248, 42, 26, 204, 98, 76, 219, 198, 189, 194, 9, 111, 80, 59, 111, 94, 150, 142, 35, 94, 33, 197, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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