Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d73e0b5c46a44e67cdf652ebc99bdf9ee2bb8712cc434474f070723f84e6293

Tx prefix hash: 5596ee583ab90a0b5e7f1308c4d26ec8cb7fb82756ab42ebf0fc9787ae150424
Tx public key: 91e8df40ca0ef0a9d86f17f92e83946ee72c2bc983287d96cdd325abc824724f
Timestamp: 1714642370 Timestamp [UCT]: 2024-05-02 09:32:50 Age [y:d:h:m:s]: 01:014:15:59:41
Block: 1013143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271413 RingCT/type: yes/0
Extra: 0191e8df40ca0ef0a9d86f17f92e83946ee72c2bc983287d96cdd325abc824724f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ff338ed48523ce31ab5a656c778aae8035a3986bfae95ad50bdb05e47d042b3 0.600000000000 1475882 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": 1013153, "vin": [ { "gen": { "height": 1013143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ff338ed48523ce31ab5a656c778aae8035a3986bfae95ad50bdb05e47d042b3" } } ], "extra": [ 1, 145, 232, 223, 64, 202, 14, 240, 169, 216, 111, 23, 249, 46, 131, 148, 110, 231, 44, 43, 201, 131, 40, 125, 150, 205, 211, 37, 171, 200, 36, 114, 79, 2, 17, 0, 0, 0, 3, 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