Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69aea23b347aab3a1afbdb47214ac135df246dc1195f97ebd80ce3a4662c72f9

Tx prefix hash: ff97ead65ee71a672e2d24e546eaebdf711eeef2c9792386a76a979e7e40a7ca
Tx public key: f2fd5b19e4546cab82563a61cc0eac002b547476b4fe4a49e760ea81b6bf9200
Timestamp: 1707013252 Timestamp [UCT]: 2024-02-04 02:20:52 Age [y:d:h:m:s]: 01:074:15:39:04
Block: 949877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314429 RingCT/type: yes/0
Extra: 01f2fd5b19e4546cab82563a61cc0eac002b547476b4fe4a49e760ea81b6bf920002110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5f7954f484f5bc60938ff0f7c7bab125a191493eaa1f611d77a8acc6194e578 0.600000000000 1408411 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": 949887, "vin": [ { "gen": { "height": 949877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5f7954f484f5bc60938ff0f7c7bab125a191493eaa1f611d77a8acc6194e578" } } ], "extra": [ 1, 242, 253, 91, 25, 228, 84, 108, 171, 130, 86, 58, 97, 204, 14, 172, 0, 43, 84, 116, 118, 180, 254, 74, 73, 231, 96, 234, 129, 182, 191, 146, 0, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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