Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bf670e66849b3b1596271ba5766e78adf1b17229f160da8773f8b4adb13e076

Tx prefix hash: 79c54571697e66a43fd51c3d14bed29b14b8afc5f438ffb2fb170b900810e290
Tx public key: f0d1b8c8f8e1d6935de97f050af00a4448f1286874248d46ee14d1a9b94b32d7
Timestamp: 1728701360 Timestamp [UCT]: 2024-10-12 02:49:20 Age [y:d:h:m:s]: 00:181:00:34:09
Block: 1129710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129155 RingCT/type: yes/0
Extra: 01f0d1b8c8f8e1d6935de97f050af00a4448f1286874248d46ee14d1a9b94b32d702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e34d49cf7d57af4f72dfbe4cbb6d277a0b237ee453b3f65ea9767827898ea149 0.600000000000 1612553 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": 1129720, "vin": [ { "gen": { "height": 1129710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e34d49cf7d57af4f72dfbe4cbb6d277a0b237ee453b3f65ea9767827898ea149" } } ], "extra": [ 1, 240, 209, 184, 200, 248, 225, 214, 147, 93, 233, 127, 5, 10, 240, 10, 68, 72, 241, 40, 104, 116, 36, 141, 70, 238, 20, 209, 169, 185, 75, 50, 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