Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 569c91c4275b94c96953eeeeb909f7a29b305e5479071f8eab65bee81c59ea1b

Tx prefix hash: 30cb41c7c5ae89cafc0962d1820a8102065225dc6391dea33a818717f1b210b5
Tx public key: 143f1b6cb05221ac94b10b128bb1a941d8228887a0e063177adf12d94ad40c07
Timestamp: 1732290516 Timestamp [UCT]: 2024-11-22 15:48:36 Age [y:d:h:m:s]: 00:001:10:35:20
Block: 1159353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1039 RingCT/type: yes/0
Extra: 01143f1b6cb05221ac94b10b128bb1a941d8228887a0e063177adf12d94ad40c070211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9ea3b52d5e9112bc3a8dcdbba585b614b8728e5e09575c17db0a8a9e33a8de6 0.600000000000 1644986 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": 1159363, "vin": [ { "gen": { "height": 1159353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9ea3b52d5e9112bc3a8dcdbba585b614b8728e5e09575c17db0a8a9e33a8de6" } } ], "extra": [ 1, 20, 63, 27, 108, 176, 82, 33, 172, 148, 177, 11, 18, 139, 177, 169, 65, 216, 34, 136, 135, 160, 224, 99, 23, 122, 223, 18, 217, 74, 212, 12, 7, 2, 17, 0, 0, 0, 1, 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