Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ca53c9bd358e1c0e2fbabd3864c3d96a87a44b6ba305e82d148d594910aca9e

Tx prefix hash: 6f79a4e83ce0615a3960fb93b930ededb5be13b0a01da178a9f15a3824362723
Tx public key: 6e3af08b84f0a084a5721efb38518b18fe8d6d5a6a97f35c8e6d6494f4e4dbf5
Timestamp: 1578807315 Timestamp [UCT]: 2020-01-12 05:35:15 Age [y:d:h:m:s]: 04:353:06:48:34
Block: 43679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1142038 RingCT/type: yes/0
Extra: 016e3af08b84f0a084a5721efb38518b18fe8d6d5a6a97f35c8e6d6494f4e4dbf5021100000007d81c26c0000000000000000000

1 output(s) for total of 439.819198954000 dcy

stealth address amount amount idx
00: 260fd057863807f0de781b59744c47c394053489f9748c9c61212cceee406881 439.819198954000 79216 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": 43689, "vin": [ { "gen": { "height": 43679 } } ], "vout": [ { "amount": 439819198954, "target": { "key": "260fd057863807f0de781b59744c47c394053489f9748c9c61212cceee406881" } } ], "extra": [ 1, 110, 58, 240, 139, 132, 240, 160, 132, 165, 114, 30, 251, 56, 81, 139, 24, 254, 141, 109, 90, 106, 151, 243, 92, 142, 109, 100, 148, 244, 228, 219, 245, 2, 17, 0, 0, 0, 7, 216, 28, 38, 192, 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