Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fcc63b1fc6e5ce5764bbbeb4cc3974d2a84d7b1e5bfda225a8feca6d9b40c27

Tx prefix hash: f798bdefede170f065943b7efd1462f17bf68f1d068a1be675b1460c5083ef21
Tx public key: a5e89489e8591cac55ad126af37d4643661cf4bbc1cd74881792731f303b6dc6
Timestamp: 1725726063 Timestamp [UCT]: 2024-09-07 16:21:03 Age [y:d:h:m:s]: 01:059:08:40:48
Block: 1105031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300829 RingCT/type: yes/0
Extra: 01a5e89489e8591cac55ad126af37d4643661cf4bbc1cd74881792731f303b6dc602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b15c86fe8a2f8eb8eb6e28d6d054a8f4b106284e4fa0a5df34120a62afb02f9f 0.600000000000 1582368 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": 1105041, "vin": [ { "gen": { "height": 1105031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b15c86fe8a2f8eb8eb6e28d6d054a8f4b106284e4fa0a5df34120a62afb02f9f" } } ], "extra": [ 1, 165, 232, 148, 137, 232, 89, 28, 172, 85, 173, 18, 106, 243, 125, 70, 67, 102, 28, 244, 187, 193, 205, 116, 136, 23, 146, 115, 31, 48, 59, 109, 198, 2, 17, 0, 0, 0, 2, 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