Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71064ee9397ed8df0a968f8c48b747407a80d93236e1e1ba5419864fe9747dee

Tx prefix hash: e51438094f24d9408c800c25caaf5aff96b1e290227b1b6f2c832909b41e31d3
Tx public key: 8835ab90760ad2c57a95adf2e894bf1cebaaff84df6e958d1eb51c5446079cfc
Timestamp: 1706635879 Timestamp [UCT]: 2024-01-30 17:31:19 Age [y:d:h:m:s]: 01:070:12:32:47
Block: 946740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311483 RingCT/type: yes/0
Extra: 018835ab90760ad2c57a95adf2e894bf1cebaaff84df6e958d1eb51c5446079cfc02110000000181d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95da3ac9f6a34fd7a28bfb9e93a431ccddd10c8318b401604bf9c8f316d796a4 0.600000000000 1405080 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": 946750, "vin": [ { "gen": { "height": 946740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95da3ac9f6a34fd7a28bfb9e93a431ccddd10c8318b401604bf9c8f316d796a4" } } ], "extra": [ 1, 136, 53, 171, 144, 118, 10, 210, 197, 122, 149, 173, 242, 232, 148, 191, 28, 235, 170, 255, 132, 223, 110, 149, 141, 30, 181, 28, 84, 70, 7, 156, 252, 2, 17, 0, 0, 0, 1, 129, 215, 29, 85, 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