Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53e91012762ba71abc3cd95130ce58ed859b24a35293c584a2d4db37bfc4da98

Tx prefix hash: ed54fbb6ed88c1de1549f5af49fdadd5d700578f943e34512b43a31e4b838d8a
Tx public key: aef0e79cdd5a6434b3adca0d0c19f0b392ab1123c0fd59272074958717cccbee
Timestamp: 1694905003 Timestamp [UCT]: 2023-09-16 22:56:43 Age [y:d:h:m:s]: 01:180:16:00:51
Block: 849690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390227 RingCT/type: yes/0
Extra: 01aef0e79cdd5a6434b3adca0d0c19f0b392ab1123c0fd59272074958717cccbee0211000000014b8f5122000000000000000000

1 output(s) for total of 0.938910863000 dcy

stealth address amount amount idx
00: 71a65a7522ac4b6d6fb2ccd8805fa384db2793e394eb1e9c1886fcc65851d038 0.938910863000 1303366 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": 849700, "vin": [ { "gen": { "height": 849690 } } ], "vout": [ { "amount": 938910863, "target": { "key": "71a65a7522ac4b6d6fb2ccd8805fa384db2793e394eb1e9c1886fcc65851d038" } } ], "extra": [ 1, 174, 240, 231, 156, 221, 90, 100, 52, 179, 173, 202, 13, 12, 25, 240, 179, 146, 171, 17, 35, 192, 253, 89, 39, 32, 116, 149, 135, 23, 204, 203, 238, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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