Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eba9706132eb2fe20a66567a595e1c03369e46378410d48153f5629c34d9abf8

Tx prefix hash: 0429723af744cfa927b4a3f7cd056378285fe7d5325ecd3d05f1a4b0cebdd43f
Tx public key: 2167f26b1f75c796f6f1da2c72cbbfc0bbb1f14c979ee15bb3ada846a5fe7280
Timestamp: 1581566875 Timestamp [UCT]: 2020-02-13 04:07:55 Age [y:d:h:m:s]: 05:007:04:21:54
Block: 63818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157966 RingCT/type: yes/0
Extra: 012167f26b1f75c796f6f1da2c72cbbfc0bbb1f14c979ee15bb3ada846a5fe7280021100000003d81c26c0000000000000000000

1 output(s) for total of 377.177073593000 dcy

stealth address amount amount idx
00: 049fd9f32a2603059cb111b6d128ddcfe18a301a27e698afefab4356a05e9b37 377.177073593000 117660 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": 63828, "vin": [ { "gen": { "height": 63818 } } ], "vout": [ { "amount": 377177073593, "target": { "key": "049fd9f32a2603059cb111b6d128ddcfe18a301a27e698afefab4356a05e9b37" } } ], "extra": [ 1, 33, 103, 242, 107, 31, 117, 199, 150, 246, 241, 218, 44, 114, 203, 191, 192, 187, 177, 241, 76, 151, 158, 225, 91, 179, 173, 168, 70, 165, 254, 114, 128, 2, 17, 0, 0, 0, 3, 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