Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14854f01da877b0f7f8eb6c7e9da1f72945e317beb2f6da941e15e50ca4675e2

Tx prefix hash: 3596d9c72dae095b20803b6851eb52a959495260080e6eee02e16915a93d8aa6
Tx public key: c714a8433c23428d51f4dffd179029c084c0461d573564c8db4b36a0f83ba2c0
Timestamp: 1735449421 Timestamp [UCT]: 2024-12-29 05:17:01 Age [y:d:h:m:s]: 00:171:12:39:50
Block: 1185505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122304 RingCT/type: yes/0
Extra: 01c714a8433c23428d51f4dffd179029c084c0461d573564c8db4b36a0f83ba2c00211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 853612dfa981f4a4d08f6ae7859447edde9367b7f78fce6911b39809d779bd3e 0.600000000000 1671978 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": 1185515, "vin": [ { "gen": { "height": 1185505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "853612dfa981f4a4d08f6ae7859447edde9367b7f78fce6911b39809d779bd3e" } } ], "extra": [ 1, 199, 20, 168, 67, 60, 35, 66, 141, 81, 244, 223, 253, 23, 144, 41, 192, 132, 192, 70, 29, 87, 53, 100, 200, 219, 75, 54, 160, 248, 59, 162, 192, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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