Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0c61430a0e45708c4ca49c466fd580d2d47b005590a42b80d854dd246cd850a

Tx prefix hash: 22e16afbdb9543a2908ad73f6856c36e4d031d4eff6e8e29c144e1843d68938f
Tx public key: 6955eec7cee072793df1779282a9917f8c8c0f8177603d62388efd58d52a6ea5
Timestamp: 1712794012 Timestamp [UCT]: 2024-04-11 00:06:52 Age [y:d:h:m:s]: 01:012:21:16:41
Block: 997788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270188 RingCT/type: yes/0
Extra: 016955eec7cee072793df1779282a9917f8c8c0f8177603d62388efd58d52a6ea50211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef44c6d7b18ae1705bf0351654f4e5489db6ba637d2b03e2efaa65b45bda23e5 0.600000000000 1458222 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": 997798, "vin": [ { "gen": { "height": 997788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef44c6d7b18ae1705bf0351654f4e5489db6ba637d2b03e2efaa65b45bda23e5" } } ], "extra": [ 1, 105, 85, 238, 199, 206, 224, 114, 121, 61, 241, 119, 146, 130, 169, 145, 127, 140, 140, 15, 129, 119, 96, 61, 98, 56, 142, 253, 88, 213, 42, 110, 165, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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