Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22573a1c468da74e7dfc9b6599c75f785ad9d5f9f5c372b5b24afa11cb869e29

Tx prefix hash: d196f489637cd300d20f8c919103b0b17ca6709fcdbafafed0e6f9d97e9c9126
Tx public key: 5dde5a33ea2b8c8f0c703c73c748626eeae1c2558e28e4bc4543a8776851e55c
Timestamp: 1738866028 Timestamp [UCT]: 2025-02-06 18:20:28 Age [y:d:h:m:s]: 00:287:07:13:25
Block: 1213538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203078 RingCT/type: yes/0
Extra: 015dde5a33ea2b8c8f0c703c73c748626eeae1c2558e28e4bc4543a8776851e55c02110000001727ff1f91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 346cd232d18c0068583f81ec47c123bdc4c923f58888308990860f1f7f8c8492 0.600000000000 1700317 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": 1213548, "vin": [ { "gen": { "height": 1213538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "346cd232d18c0068583f81ec47c123bdc4c923f58888308990860f1f7f8c8492" } } ], "extra": [ 1, 93, 222, 90, 51, 234, 43, 140, 143, 12, 112, 60, 115, 199, 72, 98, 110, 234, 225, 194, 85, 142, 40, 228, 188, 69, 67, 168, 119, 104, 81, 229, 92, 2, 17, 0, 0, 0, 23, 39, 255, 31, 145, 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