Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1755b4bdb586ef5e01439f32b1db6821858fdcc741474bb01a94f0fc53e97e36

Tx prefix hash: a02e7485402b78cc0a242516d54040cf16e96756eeda94f758554f71e8a3a035
Tx public key: 6ef2fd4e3835d48fc049dd1b9b95ca3a01e1c89b32f91bd0dc49db872343fb50
Timestamp: 1733165888 Timestamp [UCT]: 2024-12-02 18:58:08 Age [y:d:h:m:s]: 00:342:12:33:49
Block: 1166612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242324 RingCT/type: yes/0
Extra: 016ef2fd4e3835d48fc049dd1b9b95ca3a01e1c89b32f91bd0dc49db872343fb5002110000000c01491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 390dbaf30a125c047cbed3f194b112b726efe9717ca92d77aa4e3f25ba272061 0.600000000000 1652301 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": 1166622, "vin": [ { "gen": { "height": 1166612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "390dbaf30a125c047cbed3f194b112b726efe9717ca92d77aa4e3f25ba272061" } } ], "extra": [ 1, 110, 242, 253, 78, 56, 53, 212, 143, 192, 73, 221, 27, 155, 149, 202, 58, 1, 225, 200, 155, 50, 249, 27, 208, 220, 73, 219, 135, 35, 67, 251, 80, 2, 17, 0, 0, 0, 12, 1, 73, 31, 136, 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