Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2172666810d73f8f04b20a8f0aea86a3b4b7898228ae7212bbaa6a5e498a5c32

Tx prefix hash: 96237d3ccefc00a9f1ac47ff4e3aa36aebc24d29cb4d2b5339d03c9ee4be7468
Tx public key: d958f2c880935d51333763acf607d8ada3274651e34402b5ae1d9ad7eba5d09d
Timestamp: 1578810876 Timestamp [UCT]: 2020-01-12 06:34:36 Age [y:d:h:m:s]: 04:347:01:21:07
Block: 43706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137632 RingCT/type: yes/0
Extra: 01d958f2c880935d51333763acf607d8ada3274651e34402b5ae1d9ad7eba5d09d02110000000d4943cd9f000000000000000000

1 output(s) for total of 439.736197976000 dcy

stealth address amount amount idx
00: 4df1f5e5fdfd8b23128584410fbf80f16e448a2ac846f8ff17db3bce11619a5b 439.736197976000 79271 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": 43716, "vin": [ { "gen": { "height": 43706 } } ], "vout": [ { "amount": 439736197976, "target": { "key": "4df1f5e5fdfd8b23128584410fbf80f16e448a2ac846f8ff17db3bce11619a5b" } } ], "extra": [ 1, 217, 88, 242, 200, 128, 147, 93, 81, 51, 55, 99, 172, 246, 7, 216, 173, 163, 39, 70, 81, 227, 68, 2, 181, 174, 29, 154, 215, 235, 165, 208, 157, 2, 17, 0, 0, 0, 13, 73, 67, 205, 159, 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