Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3da4a3dd23584f12b2dc523327fd724ca9687e1623ca02abf9ab5e8a19bf35ae

Tx prefix hash: 343a7b173abe89cc692865c073e5d66aeb50f674add91f4f0d2b64cb26d0ab48
Tx public key: fb98f1002701ffa12c8125ae6a7de01a8708d4f84902ad7e75debf45c3715c15
Timestamp: 1763985715 Timestamp [UCT]: 2025-11-24 12:01:55 Age [y:d:h:m:s]: 00:036:17:42:32
Block: 1419086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26305 RingCT/type: yes/0
Extra: 01fb98f1002701ffa12c8125ae6a7de01a8708d4f84902ad7e75debf45c3715c150211000000038ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54dae2d0091fe29d9a52bf554a66f725d9466b1aaf1c157ea6d21c3af0e1ad43 0.600000000000 1907621 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": 1419096, "vin": [ { "gen": { "height": 1419086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54dae2d0091fe29d9a52bf554a66f725d9466b1aaf1c157ea6d21c3af0e1ad43" } } ], "extra": [ 1, 251, 152, 241, 0, 39, 1, 255, 161, 44, 129, 37, 174, 106, 125, 224, 26, 135, 8, 212, 248, 73, 2, 173, 126, 117, 222, 191, 69, 195, 113, 92, 21, 2, 17, 0, 0, 0, 3, 140, 235, 127, 9, 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