Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d5f639d02d20dc772cb4a2a64e77b55966f3ef7ba12a753a54a4b443f485110

Tx prefix hash: 48533bc259d26e73be4c34b13426bc8cd96088a2271e3c54e0113b258976adeb
Tx public key: 2db59f80cef8181da99635c03d51b7d4fbc61c628581f8e28b113069ee037b00
Timestamp: 1676651750 Timestamp [UCT]: 2023-02-17 16:35:50 Age [y:d:h:m:s]: 02:074:07:27:06
Block: 699059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574720 RingCT/type: yes/0
Extra: 012db59f80cef8181da99635c03d51b7d4fbc61c628581f8e28b113069ee037b00021100000002835e4d22000000000000000000

1 output(s) for total of 2.962970001000 dcy

stealth address amount amount idx
00: fa5f073fbcb8c0293b5a9601e358a9c46f85ed5edb4b20741a7a38fd44806760 2.962970001000 1142452 of 0

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": 699069, "vin": [ { "gen": { "height": 699059 } } ], "vout": [ { "amount": 2962970001, "target": { "key": "fa5f073fbcb8c0293b5a9601e358a9c46f85ed5edb4b20741a7a38fd44806760" } } ], "extra": [ 1, 45, 181, 159, 128, 206, 248, 24, 29, 169, 150, 53, 192, 61, 81, 183, 212, 251, 198, 28, 98, 133, 129, 248, 226, 139, 17, 48, 105, 238, 3, 123, 0, 2, 17, 0, 0, 0, 2, 131, 94, 77, 34, 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