Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0f9cca10ff5bc828fbf444deeb523792fcfdfe8b56d462c372292af6aaa92a4

Tx prefix hash: c7ccd676199a4dde1e960bf9c0eedd9b71d410aeafea7df830d46430ee7946aa
Tx public key: 31e97526cfc8eb47b8c3a39f95655646bbf03c13b4f40e625794e797ba183f2c
Timestamp: 1731237915 Timestamp [UCT]: 2024-11-10 11:25:15 Age [y:d:h:m:s]: 00:126:23:51:44
Block: 1150636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90603 RingCT/type: yes/0
Extra: 0131e97526cfc8eb47b8c3a39f95655646bbf03c13b4f40e625794e797ba183f2c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b8802ffa4113045aaab35c8762a0b2b0065f5824d229d3d8b334540f16cf7e9 0.600000000000 1635999 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": 1150646, "vin": [ { "gen": { "height": 1150636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b8802ffa4113045aaab35c8762a0b2b0065f5824d229d3d8b334540f16cf7e9" } } ], "extra": [ 1, 49, 233, 117, 38, 207, 200, 235, 71, 184, 195, 163, 159, 149, 101, 86, 70, 187, 240, 60, 19, 180, 244, 14, 98, 87, 148, 231, 151, 186, 24, 63, 44, 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