Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c75499e1c8685629560608f3db9a47dddbc53bf04371984a25a50b8a94b9629d

Tx prefix hash: 2222ff3c50b7db142ad71c45a637c7586b2b84c743c63cde828df3d368d88093
Tx public key: 4a27158110d235039ed4f0ccf86ffd2923a0a5c503ca027cb1f12da58c0e8675
Timestamp: 1735005382 Timestamp [UCT]: 2024-12-24 01:56:22 Age [y:d:h:m:s]: 00:174:02:15:54
Block: 1181847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124149 RingCT/type: yes/0
Extra: 014a27158110d235039ed4f0ccf86ffd2923a0a5c503ca027cb1f12da58c0e8675021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12167e4ad9a2d24d4ad824106b0a4b0d9977f21c8e1279615f5a5275cfb8ce6c 0.600000000000 1668276 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": 1181857, "vin": [ { "gen": { "height": 1181847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12167e4ad9a2d24d4ad824106b0a4b0d9977f21c8e1279615f5a5275cfb8ce6c" } } ], "extra": [ 1, 74, 39, 21, 129, 16, 210, 53, 3, 158, 212, 240, 204, 248, 111, 253, 41, 35, 160, 165, 197, 3, 202, 2, 124, 177, 241, 45, 165, 140, 14, 134, 117, 2, 17, 0, 0, 0, 2, 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