Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71f8fdcc8b9c3afd47616f3ca76b8928046e24d7b340aab902feb020bf6293c4

Tx prefix hash: f3f42b11da0e239c6e0ed18edc4d8606f834ea367fc81b78783f294395036a04
Tx public key: 1672312551d9d3e3adf09b8225d7a5ddbfc4d9f95d4cdc6564f0b18f39011325
Timestamp: 1718058695 Timestamp [UCT]: 2024-06-10 22:31:35 Age [y:d:h:m:s]: 00:214:19:06:46
Block: 1041470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153704 RingCT/type: yes/0
Extra: 011672312551d9d3e3adf09b8225d7a5ddbfc4d9f95d4cdc6564f0b18f390113250211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f3f2686ff6d718410fa04968bf3e257724df78cc43f8e15514f9fa64159b122 0.600000000000 1510151 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": 1041480, "vin": [ { "gen": { "height": 1041470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f3f2686ff6d718410fa04968bf3e257724df78cc43f8e15514f9fa64159b122" } } ], "extra": [ 1, 22, 114, 49, 37, 81, 217, 211, 227, 173, 240, 155, 130, 37, 215, 165, 221, 191, 196, 217, 249, 93, 76, 220, 101, 100, 240, 177, 143, 57, 1, 19, 37, 2, 17, 0, 0, 0, 1, 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