Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f600b10d264a38f8754c46849b221365797ff6fb76229ededb01b78ab4f5086f

Tx prefix hash: fbefad156c41993dfaf2122cb1c6bb3a61b7cfbf342d92e59cae8f1df0a36342
Tx public key: 1b061d18cf5d765231a14c9a1f1c684222d73ea7ed5e6e88a9a2ed666e6c9a8c
Timestamp: 1648902862 Timestamp [UCT]: 2022-04-02 12:34:22 Age [y:d:h:m:s]: 02:312:05:37:47
Block: 471636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742611 RingCT/type: yes/0
Extra: 011b061d18cf5d765231a14c9a1f1c684222d73ea7ed5e6e88a9a2ed666e6c9a8c021100000002a272b9cb000000000000000000

1 output(s) for total of 16.798650464000 dcy

stealth address amount amount idx
00: 02f2d382bdc7c91e11e99c0780f5b3b2b721c9a69934385a775a6629ca6217e9 16.798650464000 891010 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": 471646, "vin": [ { "gen": { "height": 471636 } } ], "vout": [ { "amount": 16798650464, "target": { "key": "02f2d382bdc7c91e11e99c0780f5b3b2b721c9a69934385a775a6629ca6217e9" } } ], "extra": [ 1, 27, 6, 29, 24, 207, 93, 118, 82, 49, 161, 76, 154, 31, 28, 104, 66, 34, 215, 62, 167, 237, 94, 110, 136, 169, 162, 237, 102, 110, 108, 154, 140, 2, 17, 0, 0, 0, 2, 162, 114, 185, 203, 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