Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fa40897e05fbc6cbbc3cde0524efd8afe806dfe06fcb3b40aeda322763e376d

Tx prefix hash: 5236700f45b176b9d91e54a1ab0ca4e9fde9f2c16dfb2ade558dd4ce1050276c
Tx public key: 046b1ebf00f2854d27def901931a519af170e7f81953373f63e13e0274ec8ced
Timestamp: 1722957124 Timestamp [UCT]: 2024-08-06 15:12:04 Age [y:d:h:m:s]: 00:261:03:15:22
Block: 1082066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186541 RingCT/type: yes/0
Extra: 01046b1ebf00f2854d27def901931a519af170e7f81953373f63e13e0274ec8ced02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0b829f62f22c95c77cfdec0c1e9dbf38dc8ed355e5e4ab38390a96adf3d3e54 0.600000000000 1555889 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": 1082076, "vin": [ { "gen": { "height": 1082066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0b829f62f22c95c77cfdec0c1e9dbf38dc8ed355e5e4ab38390a96adf3d3e54" } } ], "extra": [ 1, 4, 107, 30, 191, 0, 242, 133, 77, 39, 222, 249, 1, 147, 26, 81, 154, 241, 112, 231, 248, 25, 83, 55, 63, 99, 225, 62, 2, 116, 236, 140, 237, 2, 17, 0, 0, 0, 3, 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