Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dd4a5c2b7756b9b75cb16f4726cfc1fbf54daea88bfb6482cc7d4a6d59a048b

Tx prefix hash: 09ba2069087341870bbbcce8edb86da6e3e96991ea2bc9b6c7007ea18a0b249d
Tx public key: 9aae7be32c8074311d0e5682f427f8a02ba7b1c9815a3be82c15a9ae0983eb2b
Timestamp: 1735199420 Timestamp [UCT]: 2024-12-26 07:50:20 Age [y:d:h:m:s]: 00:108:04:28:42
Block: 1183452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77110 RingCT/type: yes/0
Extra: 019aae7be32c8074311d0e5682f427f8a02ba7b1c9815a3be82c15a9ae0983eb2b021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8f70087e3037acb69ad14eb43d2c63a42b968989467473fae5d58de33a0ecfa 0.600000000000 1669897 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": 1183462, "vin": [ { "gen": { "height": 1183452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8f70087e3037acb69ad14eb43d2c63a42b968989467473fae5d58de33a0ecfa" } } ], "extra": [ 1, 154, 174, 123, 227, 44, 128, 116, 49, 29, 14, 86, 130, 244, 39, 248, 160, 43, 167, 177, 201, 129, 90, 59, 232, 44, 21, 169, 174, 9, 131, 235, 43, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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