Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9822c7d5645fe6d7f7f46a2c3805aae7f3744e25fa9dc31b036d7cc7b04be5c8

Tx prefix hash: ed4b850f73245557685b484c1b536f3575f36c28e44ef156d40fc61cfa8fc41c
Tx public key: bf9c1a9fe737e6644ecdf12673f8f727e8ccf4b8423cbcaf515defa2f27a3212
Timestamp: 1718565066 Timestamp [UCT]: 2024-06-16 19:11:06 Age [y:d:h:m:s]: 00:272:14:22:27
Block: 1045675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194795 RingCT/type: yes/0
Extra: 01bf9c1a9fe737e6644ecdf12673f8f727e8ccf4b8423cbcaf515defa2f27a321202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cdf2569e7f4310440d44733b24de401ada315317b85cbe459baf7213723d97d 0.600000000000 1515310 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": 1045685, "vin": [ { "gen": { "height": 1045675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cdf2569e7f4310440d44733b24de401ada315317b85cbe459baf7213723d97d" } } ], "extra": [ 1, 191, 156, 26, 159, 231, 55, 230, 100, 78, 205, 241, 38, 115, 248, 247, 39, 232, 204, 244, 184, 66, 60, 188, 175, 81, 93, 239, 162, 242, 122, 50, 18, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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