Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7cc163f4f373c53802b28a9a022286bd952fa209c004f31990e1a49e757f293

Tx prefix hash: 838256147174f522ef3bafc9eb99dfc906df261bdce941f7d16ddff5064f9c41
Tx public key: 2bc745f1d7b8fc4ce43f556051de5f109077bd4683670b5daf5e1fcb0834d983
Timestamp: 1719618114 Timestamp [UCT]: 2024-06-28 23:41:54 Age [y:d:h:m:s]: 00:285:23:07:59
Block: 1054389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204329 RingCT/type: yes/0
Extra: 012bc745f1d7b8fc4ce43f556051de5f109077bd4683670b5daf5e1fcb0834d9830211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f5104cd31215a18bcf6ea34272b257f19c66665accb3b54a76727a1243c96fe 0.600000000000 1524750 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": 1054399, "vin": [ { "gen": { "height": 1054389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f5104cd31215a18bcf6ea34272b257f19c66665accb3b54a76727a1243c96fe" } } ], "extra": [ 1, 43, 199, 69, 241, 215, 184, 252, 76, 228, 63, 85, 96, 81, 222, 95, 16, 144, 119, 189, 70, 131, 103, 11, 93, 175, 94, 31, 203, 8, 52, 217, 131, 2, 17, 0, 0, 0, 4, 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