Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6249517af76fc285954090ad5579e618b21f7d798dfdf5e3eedeff0c1730237

Tx prefix hash: e74c58e676096bf69b26d942b450342d2842f2c22fa6c767283c6eb63c60bcc4
Tx public key: 2417ebe557ae2cfbe0b3b0179f6a34b295903098b5b3a2bd12309181e756a2d1
Timestamp: 1707468220 Timestamp [UCT]: 2024-02-09 08:43:40 Age [y:d:h:m:s]: 01:275:22:53:01
Block: 953655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455989 RingCT/type: yes/0
Extra: 012417ebe557ae2cfbe0b3b0179f6a34b295903098b5b3a2bd12309181e756a2d10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5b32ff9c846d9c9d08b5c70eba61a0d340528e964a62331c336418918641f8b 0.600000000000 1412891 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": 953665, "vin": [ { "gen": { "height": 953655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5b32ff9c846d9c9d08b5c70eba61a0d340528e964a62331c336418918641f8b" } } ], "extra": [ 1, 36, 23, 235, 229, 87, 174, 44, 251, 224, 179, 176, 23, 159, 106, 52, 178, 149, 144, 48, 152, 181, 179, 162, 189, 18, 48, 145, 129, 231, 86, 162, 209, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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