Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a03262564fe0c434ac75ec0029af9f7dad13db5870626a331c45d7d227f65d85

Tx prefix hash: f0d9e86c9226652e3d0e12f8ffc964265136491471c4e83ac2fe85cd3dd4ee6a
Tx public key: eae205bd04d40b87a6c956e82f1dbe696e8fe6845a1917031cadddc4c4dc0ed7
Timestamp: 1723479763 Timestamp [UCT]: 2024-08-12 16:22:43 Age [y:d:h:m:s]: 00:215:17:18:58
Block: 1086404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154066 RingCT/type: yes/0
Extra: 01eae205bd04d40b87a6c956e82f1dbe696e8fe6845a1917031cadddc4c4dc0ed702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c42f2a09d27822b80c3029a39a505c7b854205f2d6fc0bd39fde9468d38eee2e 0.600000000000 1561001 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": 1086414, "vin": [ { "gen": { "height": 1086404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c42f2a09d27822b80c3029a39a505c7b854205f2d6fc0bd39fde9468d38eee2e" } } ], "extra": [ 1, 234, 226, 5, 189, 4, 212, 11, 135, 166, 201, 86, 232, 47, 29, 190, 105, 110, 143, 230, 132, 90, 25, 23, 3, 28, 173, 221, 196, 196, 220, 14, 215, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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