Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4da1ee8214c6ff1837110152588e64f7767c35d2b3ec4b85ad5a3a02832d65c7

Tx prefix hash: 410ace0104f7565a858e392cbea22dbf1c2d66d2bd797ee4d51a7a9dce58245a
Tx public key: 6f14020e727f5b34d2c832f0ae2bc184b286810c5b32ad93d047654c6cd7317b
Timestamp: 1760469890 Timestamp [UCT]: 2025-10-14 19:24:50 Age [y:d:h:m:s]: 00:026:18:39:40
Block: 1389952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19174 RingCT/type: yes/0
Extra: 016f14020e727f5b34d2c832f0ae2bc184b286810c5b32ad93d047654c6cd7317b0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ce7f755f6bce3c041f45f1c2c2dc79ec6f6a2e5e4ec0330242aabcb0486c0bf 0.600000000000 1878183 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": 1389962, "vin": [ { "gen": { "height": 1389952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ce7f755f6bce3c041f45f1c2c2dc79ec6f6a2e5e4ec0330242aabcb0486c0bf" } } ], "extra": [ 1, 111, 20, 2, 14, 114, 127, 91, 52, 210, 200, 50, 240, 174, 43, 193, 132, 178, 134, 129, 12, 91, 50, 173, 147, 208, 71, 101, 76, 108, 215, 49, 123, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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