Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdcaf08789ffdab4625f05f9b9eb7dcd969cf66b38369d072814f4f23494be33

Tx prefix hash: c545ddf3b5bd5b02b5d7bd1b0f580b5e126aa360676eb54bdda0c2c7cb314e6d
Tx public key: f7b614cf7de6bf02f7fd6255d32ee878b5dc839477c8531b096c3e55297d1536
Timestamp: 1714645303 Timestamp [UCT]: 2024-05-02 10:21:43 Age [y:d:h:m:s]: 00:298:21:17:49
Block: 1013163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213618 RingCT/type: yes/0
Extra: 01f7b614cf7de6bf02f7fd6255d32ee878b5dc839477c8531b096c3e55297d15360211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 922eea7d4c54a03cfdad861958af9c0375aca02d7cf196a13492bc6091fa69ac 0.600000000000 1475906 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": 1013173, "vin": [ { "gen": { "height": 1013163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "922eea7d4c54a03cfdad861958af9c0375aca02d7cf196a13492bc6091fa69ac" } } ], "extra": [ 1, 247, 182, 20, 207, 125, 230, 191, 2, 247, 253, 98, 85, 211, 46, 232, 120, 181, 220, 131, 148, 119, 200, 83, 27, 9, 108, 62, 85, 41, 125, 21, 54, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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