Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cde69cc13e103e77331c6f86f83341816833dd93a22dde0a8cc063d1ef5cc20a

Tx prefix hash: 079b0c6e9d810165ea0621cbeaeefd14e0ac37d16ae62f17279761a750e0d782
Tx public key: fdaa6565a0d0fee1b1762e7515aae6471e5686330b23d3d50876460a684d7b79
Timestamp: 1726519429 Timestamp [UCT]: 2024-09-16 20:43:49 Age [y:d:h:m:s]: 00:116:07:48:52
Block: 1111600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83189 RingCT/type: yes/0
Extra: 01fdaa6565a0d0fee1b1762e7515aae6471e5686330b23d3d50876460a684d7b79021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a27d2bc990e1bcaaa1ee6096a076f4099d487ddda89d5fd515e749610a364d49 0.600000000000 1590621 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": 1111610, "vin": [ { "gen": { "height": 1111600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a27d2bc990e1bcaaa1ee6096a076f4099d487ddda89d5fd515e749610a364d49" } } ], "extra": [ 1, 253, 170, 101, 101, 160, 208, 254, 225, 177, 118, 46, 117, 21, 170, 230, 71, 30, 86, 134, 51, 11, 35, 211, 213, 8, 118, 70, 10, 104, 77, 123, 121, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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