Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ba3fa30fee1f8168b3400024a3698df551235ec247fcba4abd9192dfbfe91e8

Tx prefix hash: 2e70721ed8b3f5ae8d01f8be0f89c08f65a6ecfdf0b6f2771c6673b6c7179b20
Tx public key: c1232c9a8d84cc5e07ff0e1e67d384fa56180a45009a49c69c59c30f19ae903f
Timestamp: 1577991061 Timestamp [UCT]: 2020-01-02 18:51:01 Age [y:d:h:m:s]: 04:322:12:30:52
Block: 37382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119579 RingCT/type: yes/0
Extra: 01c1232c9a8d84cc5e07ff0e1e67d384fa56180a45009a49c69c59c30f19ae903f0211000000054943cd9f000000000000000000

1 output(s) for total of 461.465000099000 dcy

stealth address amount amount idx
00: 8599d62401d3eb681aaef31155d28784aeec6d57e7e8f46c5d8d8771fd5840e1 461.465000099000 63430 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": 37392, "vin": [ { "gen": { "height": 37382 } } ], "vout": [ { "amount": 461465000099, "target": { "key": "8599d62401d3eb681aaef31155d28784aeec6d57e7e8f46c5d8d8771fd5840e1" } } ], "extra": [ 1, 193, 35, 44, 154, 141, 132, 204, 94, 7, 255, 14, 30, 103, 211, 132, 250, 86, 24, 10, 69, 0, 154, 73, 198, 156, 89, 195, 15, 25, 174, 144, 63, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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