Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35f51adfaa98d61c9a2863410bf01c6468de6d6fc07cd0b0cfad51edc55514fc

Tx prefix hash: 3b0d68c09f4f91459fef19f3742c4bf4a4532d45a6fa75373e40608b0fdb5800
Tx public key: 2f75a1b0f0e49d620f7895ae718737c516a9e4b9498264848c27e583b062bc73
Timestamp: 1695644869 Timestamp [UCT]: 2023-09-25 12:27:49 Age [y:d:h:m:s]: 01:205:17:42:44
Block: 855839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408113 RingCT/type: yes/0
Extra: 012f75a1b0f0e49d620f7895ae718737c516a9e4b9498264848c27e583b062bc73021100000011e6d27f9c000000000000000000

1 output(s) for total of 0.895880669000 dcy

stealth address amount amount idx
00: e90354324d2f62a77b6557ddc735d77b186aae2b78b0e6b04a2bbd71dafe3e83 0.895880669000 1309887 of 0

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": 855849, "vin": [ { "gen": { "height": 855839 } } ], "vout": [ { "amount": 895880669, "target": { "key": "e90354324d2f62a77b6557ddc735d77b186aae2b78b0e6b04a2bbd71dafe3e83" } } ], "extra": [ 1, 47, 117, 161, 176, 240, 228, 157, 98, 15, 120, 149, 174, 113, 135, 55, 197, 22, 169, 228, 185, 73, 130, 100, 132, 140, 39, 229, 131, 176, 98, 188, 115, 2, 17, 0, 0, 0, 17, 230, 210, 127, 156, 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