Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a63daf09f11ece580ab8bb5060d6470e3f564e4532396bafad05b4d2a537451f

Tx prefix hash: 8e632846f8084372d0ed3bd17a3205fc81cb05c5b1f7fe7b8ea1c51e5223c066
Tx public key: fde24c575ea2420d437a3324e28d35b5d819bad3d00c5f2dc63cc50cf820ceca
Timestamp: 1758268922 Timestamp [UCT]: 2025-09-19 08:02:02 Age [y:d:h:m:s]: 00:111:06:28:38
Block: 1371715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79680 RingCT/type: yes/0
Extra: 01fde24c575ea2420d437a3324e28d35b5d819bad3d00c5f2dc63cc50cf820ceca021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe82bbf21a621c75699bb08a0c0f2032386478d576c2e9ed30f98f7dd36646c6 0.600000000000 1859792 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": 1371725, "vin": [ { "gen": { "height": 1371715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe82bbf21a621c75699bb08a0c0f2032386478d576c2e9ed30f98f7dd36646c6" } } ], "extra": [ 1, 253, 226, 76, 87, 94, 162, 66, 13, 67, 122, 51, 36, 226, 141, 53, 181, 216, 25, 186, 211, 208, 12, 95, 45, 198, 60, 197, 12, 248, 32, 206, 202, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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